It appears that a single query that calls Cassandra's `now()` time function may actually cause a query to write or return different times.
Is this the expected or defined behavior, and if so, why does it behave like this rather than evaluating `now()` once across an entire statement? This really affects UPDATE statements but to test it more easily, you could try something like: SELECT toTimestamp(now()) as a, toTimestamp(now()) as b FROM keyspace.table LIMIT 100; If you run that a few times, you should eventually see that the timestamp returned moves onto the next millisecond mid-query. -- *Software Engineer* Turnitin - http://www.turnitin.com t...@turnitin.com
