What is your partition type? Is it org.apache.cassandra.dht.Murmur3Partitioner?
In your repair command i do see there are two different KeySpaces MY_KEYSPACE
and SN_KEYSPACE, are these two separate key spaces or typo?
-jaydeep
On Tuesday, 27 May 2014 10:26 PM, Matthew Allen
Hi,
I have following understanding about Cassandra read repair:
* If we write with QUORUM and read with QUORUM then we do not need to
externally (nodetool) trigger read repair.
* Since we are reading + writing with QUORUM then it is safe to set
read_repair_chance=0
Check if Cassandra secondary index meets your requirement.
Thank you,
Jaydeep
From: Aklin_81 asdk...@gmail.com
To: user user@cassandra.apache.org
Sent: Sunday, 13 November 2011 12:32 PM
Subject: Fast lookups for userId to username and vice versa
I need to
Hi Riyad,
You can set replication = 5 (number of replicas) and write with CL = ONE. There
is no hard requirement from Cassandra to write with CL=ALL to replicate the
data unless you need it. Considering your example, If you write with CL=ONE
then also it will replicate your data to all 5
Cassandra write operation is atomic for all the columns/super columns for a
given row key in Column Family. So in your case not all previous operations
(assuming each operation was on separate key) will be reverted.
Thank you,
Jaydeep
From: Artem Orobets
Hi Sameer,
One example is, store all the tweets for a given user in a Column
Family, where row key is user name/user id and column name is of
TimeUUID type that represents tweet arrival time. User would generally
like to see the tweets sorted based on its arrival time. So TimeUUID
will help
Hi,
If you are looking for some utility for loading the schema they you can use
schematool command line utlity as:
$ schematool host port import|export
Thank you,
Jaydeep
From: Jim the Standing Bear standingb...@gmail.com
To: user@cassandra.apache.org
Sent:
Hi Anuya,
However, columns are not being inserted.
Do you mean to say that after insert operation you couldn't retrieve the same
data? If so, then please check the time-stamp when you reinserted after delete
operation. Your second insertion time-stamp has to be greater than the previous
One small correction in my mail below.
Second insertion time-stamp has to be greater than delete time-stamp in-order
to retrieve the data.
Thank you,
Jaydeep
From: chovatia jaydeep chovatia_jayd...@yahoo.co.in
To: user@cassandra.apache.org user
