CQL - Practical Cassandra - page 36

1371081600000
2013-06-13 00:00+0000
2013-06-13 00:00:00+0000
2013-06-13T00:00+0000
2013-06-13T00:00:00+0000
2013-06-13 00:00
2013-06-13 00:00:00
2013-06-13T00:00
2013-06-13T00:00:00
2013-06-13
2013-06-13+0000
It is important to note that when the time zone is omitted, the time zone used
will be the one that is configured for that particular Cassandra node. This could
have implications for data centers that are configured in different time zones.
When the time is omitted, the time of 00:00:00 will be used in its place.
Counters
When working with counters, it is very important to note that you cannot create
a table with columns that have a type of counter mixed with any other type.
Tables created for counters are physically separate from other types of tables. The
counter type may not be set; you can increment or decrement the counter only
by a specified amount. Counters may not be part of the PRIMARY KEY of the
table.
TimeUUID
TimeUUID types have a few extra functions that allow you to extract the time in-
formation from the TimeUUID object.
now()
The now function when executed will return a new TimeUUID with the time of
the current timestamp; this ensures that the TimeUUID created is globally unique
and contains the current time when the statement was executed. This statement is
effectively useless for WHERE clauses.