Mapper: Allow to configure date_formats only on the root object mapper
#437
Labels
Comments
|
Mapper: Allow to configure |
medcl
pushed a commit
to medcl/elasticsearch
that referenced
this issue
Jul 1, 2011
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
Fix robot guest flag * Fix robot guest flag * Merged master into dev/can/robot-guest-flag-2022-01-25 Approved-by: Gideon Avida
costin
added a commit
to costin/elasticsearch
that referenced
this issue
Dec 19, 2022
use just one method instead of two centralize the creation into Aggregator centralize the ESQL function mapping (for now) into AggregateMapper
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, one can define
date_formatson all level of object mappers (for dynamic identification of date fields). This is not easy to handle merging (like adding a new format) as well as more data stored per mapper. Move to only allow to definedate_formatson the root object mapper and it will apply to all object mappers.The text was updated successfully, but these errors were encountered: