Re: Caused by: com.datastax.driver.core.exceptions.ReadTimeoutException:

2019-04-16 Thread Mahesh Daksha
solved as we spread the data across multiple rows. Thanks, Mahesh Daksha On Wed, Apr 17, 2019 at 11:42 AM Krishnanand Khambadkone wrote: > Hi, I have a single instance cassandra server. I am trying to execute a > query with ALLOW FILTERING option. When I run this same query from cqlsh >

Re: Getting Consistency level TWO when it is requested LOCAL_ONE

2019-04-11 Thread Mahesh Daksha
().setConsistencyLevel(ConsistencyLevel.valueOf(cassandraConsistencyLevel))); The only possibility i see of such behavior is its getting overridden from some where. Thanks, Mahesh Daksha On Thu, Apr 11, 2019 at 1:43 PM Jean Carlo wrote: > Hello everyone, > > I have a case where the developers are usi

Cassandra client side versus server side query timestamp.

2019-04-11 Thread Mahesh Daksha
. Thanks, Mahesh Daksha

Re: [EXTERNAL] Issue while updating a record in 3 node cassandra cluster deployed using kubernetes

2019-04-09 Thread Mahesh Daksha
Thank you Sean for your response. We are also suspecting the same and analyzing/troubleshooting it around queries associated timestamp. Thanks, Mahesh Daksha On Tue, Apr 9, 2019 at 7:08 PM Durity, Sean R wrote: > My first suspicion would be to look at the server times in the cluster.

Issue while updating a record in 3 node cassandra cluster deployed using kubernetes

2019-04-09 Thread Mahesh Daksha
.yaml && rm ../conf/conf.yml && ./cassandra -f Please note conf.yml is basically cassandra.yml file having properties related to cassandra. Thanks, Mahesh Daksha

Re: ***UNCHECKED*** Query regarding cassandra column write time set by client Timestamp Generator

2019-04-09 Thread Mahesh Daksha
tain confidential and legally >> privileged information. If you are not the intended recipient, do not copy >> or disclose its content, but please reply to this email immediately and >> highlight the error to the sender and then immediately delete the message. >> >>

Re: ***UNCHECKED*** Query regarding cassandra column write time set by client Timestamp Generator

2019-04-09 Thread Mahesh Daksha
going to overwite the same. This all information is needed as out update statements going silent (not reflecting any changes) in database. Not even returning any error or exception. Thanks, Mahesh Daksha On Tue, Apr 9, 2019 at 2:46 PM Ben Slater wrote: > Not in the logs but I think you should

***UNCHECKED*** Query regarding cassandra column write time set by client Timestamp Generator

2019-04-08 Thread Mahesh Daksha
time associated by with updated columns in the update query (sent by cient). Or if there is any other way I can log the same at client itself. Basically I want to see the write time sent by client to cassandra cluster. Thanks, Mahesh Daksha