[
https://issues.apache.org/jira/browse/CASSANDRA-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107897#comment-13107897
]
Sylvain Lebresne commented on CASSANDRA-3227:
---------------------------------------------
Works for me but more because "we either do it now or never and leaving it to
milliseconds would really sucks" than out of sheer enthusiasm towards the idea.
As for the patch, I'm not too sure about this clientState.getTimestamp(). A
clientState is a potentially a long leaving object, it lasts as long as the
connection to a given client last. Since the patch only initialize to the
current time but then update by +1 on every call disregarding of the actual
time, it seems the timestamp will get completely desynchronized quickly. Or am
I misunderstanding this ?
> 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
