cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Boule (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5870) CQLSH not showing milliseconds in timestamps
Date Sat, 10 Aug 2013 00:08:47 GMT


Ben Boule commented on CASSANDRA-5870:

The time format does not support milliseconds unless there is an undocumented way to do it.
 It seems important to be able to read the complete value of the data without the tool getting
in the way.  
> CQLSH not showing milliseconds in timestamps
> --------------------------------------------
>                 Key: CASSANDRA-5870
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>         Environment: Linux
>            Reporter: Ben Boule
>            Priority: Minor
>             Fix For: 1.2.5
> CQLSH does not include the milliseconds portion of the timestamp when outputting query
results.  For example on my system a time might be displayed like this:
> "2013-08-09 10:55:58-0400" for a time stored in cassandra as: 1376060158267
> We've found this extremely annoying when dealing with time series data as it will make
records which occurred at different times appear to occur at the same time.
> I'm submitting a patch, the existing formatting code already has handling of some versions
of python which do not support formatting time zones, I'm not sure which versions of python
can format seconds+milliseconds so I attempted to supply something which will work with any
time_format string and does not depend on the system library.
> The above time with the patch will format like this:
> "2013-08-09 10:55:58.267-0400"

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message