[CASSANDRA-5870] CQLSH not showing milliseconds in timestamps

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Won't Fix
• Fix Version/s: 1.2.9
• Component/s: Legacy/Tools

Environment

Linux

• Severity: Low
• Assignee: Unassigned
• Reporter: Ben Boule

Reviewers

Aleksey Yeschenko

• Created: 09/Aug/13 18:14
• Updated: 16/Apr/19 09:32
• Resolved: 16/Aug/13 17:31

Description

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"

Issue Links

• is superceded by: CASSANDRA-10428 cqlsh: Include sub-second precision in timestamps by default
• relates to: CASSANDRA-10428 cqlsh: Include sub-second precision in timestamps by default