[
https://issues.apache.org/jira/browse/CASSANDRA-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107912#comment-13107912
]
Jonathan Ellis commented on CASSANDRA-3227:
-------------------------------------------
{code}
+ public long getTimestamp()
+ {
+ long current = System.currentTimeMillis() * 1000;
+ clock = clock >= current ? clock + 1 : current;
+ return clock;
+ }
{code}
I may be missing something obvious, but my intention was to only use the +1
path if it needs to to avoid a conflict. (And as soon as wall-clock time
exceeds the +1 path, it switches back.)
> cassandra-cli use micro second timestamp, but CQL use milli second
> ------------------------------------------------------------------
>
> Key: CASSANDRA-3227
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3227
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 0.8.0
> Reporter: Sabro Boucher
> Assignee: Jonathan Ellis
> Labels: cql
> Fix For: 1.0.0
>
> Attachments: 3227.txt
>
>
> cassandra-cli set micro second timestamp by FBUtilities.timestampMicros. But
> CQL insert or update operation set milli second timestamp by
> AbstractModification.getTimestamp.
> If you register data by cassandra-cli, you can't update data by CQL. Because
> CQL timestamp is judged as past time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
