Quick Values aggregation converts timestamp to long #4509
Comments
|
In fact, this happens for a single quickvalues analysis on timestamp fields, too. |
|
@lennartkoopmann this is related to #4288, which is already fixed in master. I guess the question is to see if this is important enough to be included in 2.4.2 /cc: @bernd |
|
@edmundoa This should go into 2.4.2, yes. 👍 |
ghost
added
the
bernd
pushed a commit
that referenced
this issue
Jan 24, 2018
* pass all stacked fields into QuickValuesVisualization with that information we can properly format the timestamp even if it isn't the first field still has issues with timezone conversions * Pass timestamp to format directly Stacked fields have a different object structure as regular fields, so we can't rely on an object key being there. * Do not convert timestamp to UTC `DateTime` will convert the value to the user timezone, which is what we want to display. * include stacked fields in quick values title use correct default prop name * create stacked fields array on the fly if the caller doesn't give us the fields this is the case for widgets, because the container doesn't know what to pass Fixes #4509
bernd
pushed a commit
that referenced
this issue
Jan 24, 2018
* pass all stacked fields into QuickValuesVisualization with that information we can properly format the timestamp even if it isn't the first field still has issues with timezone conversions * Pass timestamp to format directly Stacked fields have a different object structure as regular fields, so we can't rely on an object key being there. * Do not convert timestamp to UTC `DateTime` will convert the value to the user timezone, which is what we want to display. * include stacked fields in quick values title use correct default prop name * create stacked fields array on the fly if the caller doesn't give us the fields this is the case for widgets, because the container doesn't know what to pass Fixes #4509 (cherry picked from commit 272604a)
bernd
pushed a commit
that referenced
this issue
Jan 24, 2018
correctly convert back to UTC when timestamp comes from message list "Add to search" button previously only the quickvalues source was correct Refs #4509
bernd
pushed a commit
that referenced
this issue
Jan 24, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running a stacked quickvalues analysis, where the second field is a timestamp, the values are returned as
long/ UNIX timestamps and no a human readable format like ISO8601.Steps to Reproduce (for bugs)
Your Environment
The text was updated successfully, but these errors were encountered: