Usually, you have nothing to do. Changes will be synced to every nodes
automatically.
2015-03-12 13:21 GMT+08:00 Ajay :
> Hi,
>
> Are there any steps to do (like nodetool or restart node) or any
> precautions after schema changes are done in a column family say adding a
> new column or modifying
Hi,
Are there any steps to do (like nodetool or restart node) or any
precautions after schema changes are done in a column family say adding a
new column or modifying any table properties?
Thanks
Ajay
Don't use the version as your timestamp. It's possible, but you'll end up
with problems when attempting to overwrite or delete entries.
Instead, make the version part of the primary key:
CREATE TABLE document_store (document_id bigint, version int, document
text, PRIMARY KEY (document_id, versio
Hi!
I have 2 questions related to our current benchmarking afforts:
1) We use C* v2.1.2 and we have the following keyspaces
*|cqlsh> SELECT * FROM system.schema_keyspaces;
keyspace_name| durable_writes| strategy_class| strategy_options
---++--
Hi,
I think that your clocks are not in sync. Do you have ntp on all your
nodes up and running with low offset? If not, setup ntp as first
probable solution. Cassandra relies on accurate clocks on all cluster
nodes for it's (internal) timestamps.
Do you see any error while writing? Or just w
Hi Gudmundur, each write and overwrite has a timestamp associated with it (you
can see these timestamps using the WRITETIME function). This timestamp is
provided by the Cassandra server if you don't explicitly supply it yourself
(which, judging by your queries, you are not). If the timestamp o
What happens if you use "update where." rather than insert?
On Wed, Mar 11, 2015 at 7:58 PM, Guðmundur Örn Jóhannsson <
gudmundur@gmail.com> wrote:
> I have a 3 node cluster of Cassandra version 2.0.9. My keyspace
> replication factor is 3 and I'm querying with consistency level ALL.
>
>
I have a 3 node cluster of Cassandra version 2.0.9. My keyspace replication
factor is 3 and I'm querying with consistency level ALL.
Problem: When I do an insert to overwrite an old row, the old data still
appears in all select queries! This does not apply to all cases, just a
subset of the rows i
Hi,
While adding a Cassandra node using OpsCenter (which is recommended), the
versions of Cassandra (Datastax community edition) shows only 2.0.9 and not
later versions in 2.0.x. Is there a reason behind it? 2.0.9 is recommended
than 2.0.11?
Thanks
Ajay
