Not really, I've passed on the comments to the doc teams.
The column timestamp is just a 64 bit int like I said.
Cheers
-
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 29/04/2013, at 10:06 AM, Michael Theroux
Hello,
Just wondering if I can get a quick clarification on some simple CQL. We
utilize Thrift CQL Queries to access our cassandra setup. As clarified in a
previous question I had, when using CQL and Thrift, timestamps on the cassandra
column data is assigned by the server, not the client,
I think this is some confusion about the two different usages of timestamp.
The timestamp stored with the column value (not a column of timestamp type) is
stored using microsecond scale, it's just a 64 bit int we do not use it as a
time value. Each mutation in a single request will have a
Yes, that does help,
So, in the link I provided:
http://www.datastax.com/docs/1.0/references/cql/UPDATE
It states:
You can specify these options:
Consistency level
Time-to-live (TTL)
Timestamp for the written columns.
Where timestamp is a link to Working with dates and times and mentions the
