Open Karakatiza666 opened 1 month ago
Calcite itself has some bugs related to sub-milisecond times, so our SQL docs claim we only support up to milliseconds. https://issues.apache.org/jira/browse/CALCITE-5919 This may be very difficult to fix in Calcite, so we'll live with this for a while.
I had secops demo generate TIMESTAMP values with microseconds, sometimes that crashes the UI when browsing the data (until my open PRs get merged). Despite the Calcite issue we would like to have microsecond support sometime, right?
Describe the bug WebConsole does not support serialization microseconds in SQL TIMESTAMP, the data gets truncated to milliseconds
To Reproduce
Additional context The issue is caused by Day.js library not being able to store microseconds. It needs to be replaced with an alternative. Temporary workaround is truncating microseconds down to milliseconds. Additionally, the TIMESTAMP value editor component needs to be updated to support entry of microseconds.