cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8538) Clarify default write time timestamp for CQL insert and update
Date Fri, 06 Feb 2015 22:50:35 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310091#comment-14310091
] 

Tyler Hobbs commented on CASSANDRA-8538:
----------------------------------------

I've clarified the default timestamp behavior in the CQL3 docs as committ {{08deff70a0}}.

CASSANDRA-7123 already clarified the batch timestamp behavior.  Let me know if you need something
else there.

bq. 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.

I'm not sure what you mean.

> Clarify default write time timestamp for CQL insert and update
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-8538
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8538
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Documentation & website
>            Reporter: Jack Krupansky
>            Assignee: Tyler Hobbs
>            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
else?
> 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
(v6.3.4#6332)

Mime
View raw message