cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evan Prothro (JIRA)" <>
Subject [jira] [Comment Edited] (CASSANDRA-5870) CQLSH not showing milliseconds in timestamps
Date Wed, 13 Apr 2016 14:09:25 GMT


Evan Prothro edited comment on CASSANDRA-5870 at 4/13/16 2:09 PM:

Thanks for the update, Tyler!

was (Author: eprothro):
Fixed in 10428.

> 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.9
> 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 was sent by Atlassian JIRA

View raw message