Re: What's the format of Cassandra's timestamp, microsecond or millisecond?

[Jeff Jirsa]

The timestamp is arbitrary precision, selected by the client. If you’re seeing 
milliseconds on some data and microseconds on others, then you have one client 
that’s using microseconds and another on milliseconds – adjust your clients.



From:  "yhq...@sina.com"
Reply-To:  "user@cassandra.apache.org", "yhq...@sina.com"
Date:  Sunday, August 9, 2015 at 10:40 PM
To:  user
Subject:  What's the format of Cassandra's timestamp, microsecond or 
millisecond?

Hi, All:

    When I use cassandra.thrift API to manipulate the data, the timestamp is in 
millisecond. It can be verified in cli:

[default@ks_wwapp] get cf_user['100031'];
=> (super_column=01#uid#,

     (name=0#d#, value=bf86010000000000, timestamp=1438689394196))



   When I use cli to set a column, the timestamp is in microseconds. Such as:

[default@ks_wwapp] get cf_user['100049'];
=> (super_column=sc_name,

     (name=c_name, value=635f76616c7565, timestamp=1439184495344000))



Now, I can't use cassandra.thrift API to update the key 100049. 

What's wrong with cassandra?



Thanks!

smime.p7s
Description: S/MIME cryptographic signature