Problem running select with partial partition keys in version 3.3

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 wor

No schema agreement from live replicas

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 com.datastax.driver.core

Keyspace name length

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

Keyspace creation taking 4-5 minutes

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 and

Re: Column value not getting updated

-the-problem/ * https://blog.logentries.com/2014/03/synchronizing-clocks-in-a-cassandra-cluster-pt-2-solutions/ -Mark On Tue, Mar 31, 2015 at 5:59 PM, Saurabh Sethi mailto:saurabh_se...@symantec.com>> wrote: That’s what I found out that the clocks were not in sync. But I have setup NTP on all 3

Re: Column value not getting updated

client timestamps explicitly. On Tue, Mar 31, 2015 at 3:23 PM, Saurabh Sethi mailto: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 of the columns. After updating, unit tes

Column value not getting updated

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 QueryBuilder

Newly added column not visible

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

Re: Unable to create a keyspace

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 mailto:cne...@yahoo.com>> Reply-To: "user@cassandra.apache.org" mailto:user@cassandra.apache.org>>, Jan mailto:cne...@yahoo.com>> Date

Re: Unable to create a keyspace

g>> 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" mailto:saurabh_

Re: Unable to create a keyspace

disconnect during the metadata refresh following the schema change. If this yields further information, please raise the issue on the driver's user mailing list. Adam Holmberg On Wed, Jan 28, 2015 at 8:19 PM, Saurabh Sethi mailto:saurabh_se...@symantec.com>> wrote: I have a 3 node C

Unable to create a keyspace

I have a 3 node Cassandra 2.1.0 cluster and I am using datastax 2.1.4 driver to create a keyspace followed by creating a column family within that keyspace from my unit test. But I do not see the keyspace getting created and the code for creating column family fails because it cannot find the k