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
Hello all,
When I select a timestamp as JSON from Cassandra, the string representation
lacks the timezone information, both via CQLSH and the Java Driver:
cqlsh:events> select toJson(created_at) AS created_at from
event_by_patient_timestamp ;
created_at
---
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 –
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 <
