cassandra-commits mailing list archives

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


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:
>             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:


View raw message