Re: client time stamp - force to be continuously increasing?

> Since this solution is from the driver, is it correct to assume that although this could potentially fix the issue within a single (client) session, it could not fix it for a pool of clients, where client A sent the first update and client B sent the 2nd one (because driver session doesn't share

Re: client time stamp - force to be continuously increasing?

1:28 AM Subject: Re: client time stamp - force to be continuously increasing? Hi, Among the ideas worth exploring, please note that the DataStax Java driver for Cassandra now includes a modified version of its monotonic timestamp generators that will indeed strive to provide rigorously

Re: client time stamp - force to be continuously increasing?

Hi, Among the ideas worth exploring, please note that the DataStax Java driver for Cassandra now includes a modified version of its monotonic timestamp generators that will indeed strive to provide rigorously increasing timestamps, even in the event of a system clock skew (in which case, they

Re: client time stamp - force to be continuously increasing?

to clarify - the currentRecordTs would be saved on a field on the record being persisted From: Jen Smith To: "user@cassandra.apache.org" Sent: Thursday, May 12, 2016 10:32 AM Subject: client time stamp - force to be continuously