cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-8538) Clarify default write time timestamp for CQL insert and update
Date Sat, 27 Dec 2014 15:56:13 GMT
Jack Krupansky created CASSANDRA-8538:

             Summary: Clarify default write time timestamp for CQL insert and update
                 Key: CASSANDRA-8538
             Project: Cassandra
          Issue Type: Improvement
          Components: Documentation & website
            Reporter: Jack Krupansky
            Priority: Minor

The current CQL spec (and downstream doc) says that the default timestamp for write time for
CQL inserts and updates is "the current time of the insertion", but that is somewhat vague
and non-specific. In particular, is that the time when the coordinator node parses the CQL
statement, or... when the row is inserted or updated on the target nodes, or... something

In particular, if the coordinator doesn't own the token of the primary key, will the owning
node set the write time or does the coordinator node do that?

Obviously the application can set an explicit TIMESTAMP, but this issue is concerned with
the default if that explicit option is not used.

Also, will all replicas of the insert or update share the precisely same write time, or will
they reflect the actual time when each particular replica row is inserted or updated on each
of the replica nodes?

Finally, if a batch statement is used to insert or update multiple rows, will they all share
the same write time (e.g., the time the batch statement was parsed) or when each replica row
is actually inserted or updated on the target (if the coordinator node does not own the token
of the partition key) or replica nodes?

It would also be helpful if the tracing option was specific as to which time is the official
write time for the insert or update.

This message was sent by Atlassian JIRA

View raw message