We just upgraded our cluster to version 3.3 and I am not able to run select or
delete statements using partial partition keys in where clause.
It asks me to provide all the partition keys.
But I have only partial partition key info (1 out of two columns) when running
a select.
Is there any
We have a 3 node Cassandra cluster (version 2.2.0). Two of the nodes are in one
subnet and third one in different subnet.
Replication factor is 2 and two of the nodes are seed nodes. Consistency level
for everything is QUORUM.
We are getting the following warning:
WARN
Apache’s Cassandra code validates the keyspace name length for max 48
characters whereas Datastax’s documentation says keyspace name should be 32 or
fewer characters.
Which of these is correct?
Thanks,
Saurabh
We have a 3 node cassandra 2.1.2 development cluster on which we frequently do
a lot of keyspace creation and deletion. But after couple of days, we observed
that keyspace creation is taking in order of 4-5 minutes.
Anyone has any idea what might be causing it?
FYI, if I run repair, cleanup
is in sync or set the client timestamps
explicitly.
On Tue, Mar 31, 2015 at 3:23 PM, Saurabh Sethi
saurabh_se...@symantec.commailto:saurabh_se...@symantec.com wrote:
I have written a unit test that creates a column family, inserts a row in that
column family and then updates the value of one
I have written a unit test that creates a column family, inserts a row in that
column family and then updates the value of one of the columns.
After updating, unit test immediately tries to read the updated value for that
column, but Cassandra returns the old value.
* I am using
I have a 3 node cluster running Cassandra version 2.1.2. Through my unit test,
I am creating a column family with 3 columns, inserting a row, asserting that
the values got inserted and then truncating the column family.
After that I am adding a fourth column to the column family and inserting a
Thanks Carlos for pointing that out. The clock on one of the nodes was not in
sync and fixing that solved the issue.
From: Jan cne...@yahoo.commailto:cne...@yahoo.com
Reply-To: user@cassandra.apache.orgmailto:user@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org,
@cassandra.apache.org
Subject: Re: Unable to create a keyspace
Saurabh a vague suggestion when you are dropping can you wait for sometime to
let the change propagate to other node.Also I see a replication factor 1 but
you have 3 nodes
On Jan 31, 2015 6:28 AM, Saurabh Sethi
saurabh_se
