You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since upgrading to 0.10.1, queries using the CLI (influx) return results with the time as an integer - 10, 13,16 or 19 digits, depending on the setting of 'precision'. Previous versions (I'm not sure when the behaviour changed) would output the full timestamp in human-readable format (e.g. "2016-02-29T23:59:59Z"). This might be linked to #4065 in which case, the change was in 0.9.5.
The full timestamp is much more user-friendly and allows for quick checking of queries, data integrity, etc. csv output to Excel is pretty-much useless without a proper timestamp.
Please revert to full timestamps or allow the format to be configurable.
The text was updated successfully, but these errors were encountered:
I think what s1m0 wanted to say is that display format should be separated from input format, i.e. that the display from select should use rfc3339 (or be user configurable), no matter what precision was used as input. I.e. that display and input should be two separate things.
Frankly guys (user feedback ahead) - timestamp input is the most confusing part for an influxdb newcomer, which is strange since it's a timeseries database. It should be either fixed to work in a consistent and predictable manner for both input and display, or better documented. Is there a way to contribute to your documentation?
Since upgrading to 0.10.1, queries using the CLI (influx) return results with the time as an integer - 10, 13,16 or 19 digits, depending on the setting of 'precision'. Previous versions (I'm not sure when the behaviour changed) would output the full timestamp in human-readable format (e.g. "2016-02-29T23:59:59Z"). This might be linked to #4065 in which case, the change was in 0.9.5.
The full timestamp is much more user-friendly and allows for quick checking of queries, data integrity, etc. csv output to Excel is pretty-much useless without a proper timestamp.
Please revert to full timestamps or allow the format to be configurable.
The text was updated successfully, but these errors were encountered: