cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3227) cassandra-cli use micro second timestamp, but CQL use milli second
Date Mon, 19 Sep 2011 08:46:08 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107701#comment-13107701
] 

Sylvain Lebresne commented on CASSANDRA-3227:
---------------------------------------------

I think this breaks rolling upgrade for anyone using CQL, since during the time where this
is a mix a node pre and post this patch, columns will get either micro or milli seconds timestamps
depending on the coordinator. 

> 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

        

Mime
View raw message