[
https://issues.apache.org/jira/browse/CASSANDRA-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112150#comment-13112150
]
Sabro Boucher commented on CASSANDRA-3227:
------------------------------------------
Thank you. The patch fixed the problem.
"aa-bb" is registered in unpatched cassandra.
"cc-dd" is registered in patched cassandra.
{noformat}
[default@QuestWorld] list Globalization;
Using default limit of 100
-------------------
RowKey: 537570706f72746564
=> (column=aa-bb, value=cc, timestamp=1316640431837)
=> (column=cc-dd, value=ee, timestamp=1316640612801000)
=> (column=en-UK, value=en, timestamp=1316356279874416)
=> (column=en-US, value=en, timestamp=1312220986047000)
=> (column=fr-FR, value=fl, timestamp=1316356768334)
=> (column=ja-JP, value=ja, timestamp=1312220978873000)
=> (column=ko-kr, value=no, timestamp=1316356622692000)
=> (column=mm-nn, value=ss, timestamp=1316640580750399)
=> (column=yy-zz, value=xx, timestamp=1316640399778399)
-------------------
RowKey: ffffffffed
=> (column=it-CH, value=it, timestamp=1316356541245000)
2 Rows Returned.
{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
