It's cqlsh that converts timestamps to UTC and adds the timezone but for
JSON it can't do that because the conversion to JSON is done by Cassandra.
I've filed https://issues.apache.org/jira/browse/CASSANDRA-11137 to discuss
further.
On Mon, Feb 8, 2016 at 7:53 PM, Alexandre Dutra <
alexandre.du..
Sorry,
I mistakenly thought that we were on the Java driver mailing list, my
apologies. I also think you should definitely file a Jira ticket and ask
JSON timestamps generated server-side to be 1) formatted with a format that
mentions the timezone and 2) formatted preferably with UTC, not the JVM
Hi Alexandre.
I wrote to ‘user@cassandra.apache.org’.
Re the actual problem: I am aware of the fact that C* does not store (need not
store) the timezone as it is persisted as a Unix epoche timestamp. Not
delivering a timezone in the JSON text representation would be OKish if the
text represent
Hello Ralf,
First of all, Cassandra stores timestamps without timezone information, so
it's not possible to retrieve the original timezone used when inserting the
value.
CQLSH uses the python driver behind the scenes, and my guess is that the
timestamp formatting is being done driver-side – hence
