so the coordinator node of a given request sets the timestamp unless
overridden by the client (which you can do on a per statement basis), while
you can move all of your timestamps to client side, eventually as you add
more clients you have a similar problem set and will still have to use NTP
to
Hi, all
I write a program to test the cassandra2.1. I have 6 nodes cluster.
First, I insert 1 million row data into cassandra. the row key from 1 to
100.
Then I run my test program. My test program first delete(use batch mutate)
the row and insert (use batch mutate) that row,
What RF?
Is the update and read immediately after the delete and insert, or is the
read after doing all the updates?
Is the delete and insert done with a single batch?
-- Jack Krupansky
On Thu, Dec 25, 2014 at 4:14 AM, yhq...@sina.com wrote:
Hi, all
I write a program to test the
Hi, all: The test program first insert one row and then delete it, then read
it to compare. The test program run this flow row by row, not batch.
Today I found the problem is caused by the deletion timestamp. The machine
running the test program may not be time sync with cassandra
