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
Is your feature request related to a problem? Please describe.
Currently, in case of multiple datetime field formats either specified by user or as part of default datetime format the stored milliseconds-since-the-epoch gets converted back to string using the first format whenever any search query is made. For eg. if the documents have datetime field without any user specified format and the value of the datetime field in the doc is in epoch_millis format but when the epoch get converted back to string during search it'll always be printed in strict_date_optional_time format because in the default date format "strict_date_optional_time||epoch_millis" optional time format is the first one.
Is your feature request related to a problem? Please describe.
Currently, in case of multiple datetime field formats either specified by user or as part of default datetime format the stored
milliseconds-since-the-epoch
gets converted back to string using the first format whenever any search query is made. For eg. if the documents have datetime field without any user specified format and the value of the datetime field in the doc is inepoch_millis
format but when the epoch get converted back to string during search it'll always be printed instrict_date_optional_time
format because in the default date format"strict_date_optional_time||epoch_millis"
optional time format is the first one.This implicit assumption has been stated in ES public documentation
Describe the solution you'd like
User should be able to define a print format in the datetime field mapping
The text was updated successfully, but these errors were encountered: