You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/09/18 18:20:08 UTC

[jira] [Updated] (CASSANDRA-3227) cassandra-cli use micro second timestamp, but CQL use milli second

     [ https://issues.apache.org/jira/browse/CASSANDRA-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-3227:
--------------------------------------

          Component/s: API
    Affects Version/s: 0.8.0
        Fix Version/s: 1.0.0
                       0.8.7
             Assignee: Jonathan Ellis

> 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
>             Fix For: 0.8.7, 1.0.0
>
>
> 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