[
https://issues.apache.org/jira/browse/CASSANDRA-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-3227:
--------------------------------------
Attachment: 3227.txt
{noformat}
+ - CQL inserts/updates now generate microsecond resolution timestamps
+ by default, instead of millisecond.
{noformat}
Adds ClientState.getTimestamp to go the extra mile:
{noformat}
+ /**
+ * This clock guarantees that updates from a given client will be ordered
in the sequence seen,
+ * even if multiple updates happen in the same millisecond. This can be
useful when a client
+ * wants to perform multiple updates to a single column.
+ */
{noformat}
> 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
