-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow dots in field names for mappings API #19443
Labels
>enhancement
help wanted
adoptme
:Search Foundations/Mapping
Index mappings, including merging and defining field types
Team:Search Foundations
Meta label for the Search Foundations team in Elasticsearch
v5.0.0-beta1
Comments
rjernst
added
help wanted
adoptme
:Search Foundations/Mapping
Index mappings, including merging and defining field types
labels
Jul 15, 2016
Do you mean that a mapping like this:
should be parsed as:
? |
@jpountz Yes, exactly. |
Discussed with @rjernst and @colings86, it seems that we could do it reasonably easily by pre-processing the map that stores the mapping it DocumentMapperParser. |
jpountz
added a commit
to jpountz/elasticsearch
that referenced
this issue
Aug 3, 2016
This commit adds the inner objects at parsing time by recursively walking the map that stores the mappings. Closes elastic#19443
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this issue
Aug 9, 2016
This change adds support for treating dots in field names found in mappings as path separators, like was previously done for dynamic mappings and document parsing. closes elastic#19443
teapot9
added a commit
to teapot9/graylog2-server
that referenced
this issue
Apr 13, 2023
Elasticsearch does not allow "." characters in field names since version 2.0. Support has been restored since version 5.0. For compatibility, graylog replaces "." with "_". However, when Elasticsearch >= 5.0 is used, this is unnecessary. For instance, Wazuh Indexer from the Wazuh project is forked from Opensearch 1.3. The character replacement causes issues with Wazuh, as the Dashboard expects dots as separator in the field name. This adds the option `replace_dots_in_field_names` to revert this behavior and allow the use of ".". The replacement is enabled by default for compatibility with existing graylog configurations. The extractor configuration in the web interface has been modified to show a warning when the user inputs a "." in the "Key separator" field. Closes: Graylog2#4583 Closes: Graylog2#6588 Closes: Graylog2#13043 Closes: Graylog2#14901 Bug: elastic/elasticsearch#19443
9 tasks
teapot9
added a commit
to teapot9/graylog2-server
that referenced
this issue
Apr 13, 2023
Elasticsearch does not allow "." characters in field names since version 2.0. Support has been restored since version 5.0. For compatibility, graylog replaces "." with "_". However, when Elasticsearch >= 5.0 is used, this is unnecessary. For instance, Wazuh Indexer from the Wazuh project is forked from Opensearch 1.3. The character replacement causes issues with Wazuh, as the Dashboard expects dots as separator in the field name. This adds the option `replace_dots_in_field_names` to revert this behavior and allow the use of ".". The replacement is enabled by default for compatibility with existing graylog configurations. The extractor configuration in the web interface has been modified to show a warning when the user inputs a "." in the "Key separator" field. Closes: Graylog2#4583 Closes: Graylog2#6588 Closes: Graylog2#13043 Closes: Graylog2#14901 Bug: elastic/elasticsearch#19443
teapot9
added a commit
to teapot9/graylog2-server
that referenced
this issue
Apr 14, 2023
Elasticsearch does not allow "." characters in field names since version 2.0. Support has been restored since version 5.0. For compatibility, graylog replaces "." with "_". However, when Elasticsearch >= 5.0 is used, this is unnecessary. For instance, Wazuh Indexer from the Wazuh project is forked from Opensearch 1.3. The character replacement causes issues with Wazuh, as the Dashboard expects dots as separator in the field name. This adds the option `replace_dots_in_field_names` to revert this behavior and allow the use of ".". The replacement is enabled by default for compatibility with existing graylog configurations. The extractor configuration in the web interface has been modified to show a warning when the user inputs a "." in the "Key separator" field. Closes: Graylog2#4583 Closes: Graylog2#6588 Closes: Graylog2#13043 Closes: Graylog2#14901 Bug: elastic/elasticsearch#19443
teapot9
added a commit
to teapot9/graylog2-server
that referenced
this issue
May 2, 2023
Elasticsearch does not allow "." characters in field names since version 2.0. Support has been restored since version 5.0. For compatibility, graylog replaces "." with "_". However, when Elasticsearch >= 5.0 is used, this is unnecessary. For instance, Wazuh Indexer from the Wazuh project is forked from Opensearch 1.3. The character replacement causes issues with Wazuh, as the Dashboard expects dots as separator in the field name. This adds the option `replace_dots_in_field_names` to revert this behavior and allow the use of ".". The replacement is enabled by default for compatibility with existing graylog configurations. The extractor configuration in the web interface has been modified to show a warning when the user inputs a "." in the "Key separator" field. Closes: Graylog2#4583 Closes: Graylog2#6588 Closes: Graylog2#13043 Closes: Graylog2#14901 Bug: elastic/elasticsearch#19443
teapot9
added a commit
to teapot9/graylog2-server
that referenced
this issue
May 4, 2023
Elasticsearch does not allow "." characters in field names since version 2.0. Support has been restored since version 5.0. For compatibility, graylog replaces "." with "_". However, when Elasticsearch >= 5.0 is used, this is unnecessary. For instance, Wazuh Indexer from the Wazuh project is forked from Opensearch 1.3. The character replacement causes issues with Wazuh, as the Dashboard expects dots as separator in the field name. This adds the option `replace_dots_in_field_names` to revert this behavior and allow the use of ".". The replacement is enabled by default for compatibility with existing graylog configurations. The extractor configuration in the web interface has been modified to show a warning when the user inputs a "." in the "Key separator" field. Closes: Graylog2#4583 Closes: Graylog2#6588 Closes: Graylog2#13043 Closes: Graylog2#14901 Bug: elastic/elasticsearch#19443
teapot9
added a commit
to teapot9/graylog2-server
that referenced
this issue
May 4, 2023
Elasticsearch does not allow "." characters in field names since version 2.0. Support has been restored since version 5.0. For compatibility, graylog replaces "." with "_". However, when Elasticsearch >= 5.0 is used, this is unnecessary. For instance, Wazuh Indexer from the Wazuh project is forked from Opensearch 1.3. The character replacement causes issues with Wazuh, as the Dashboard expects dots as separator in the field name. This adds the option `replace_dots_in_field_names` to revert this behavior and allow the use of ".". The replacement is enabled by default for compatibility with existing graylog configurations. The extractor configuration in the web interface has been modified to show a warning when the user inputs a "." in the "Key separator" field. Closes: Graylog2#4583 Closes: Graylog2#6588 Closes: Graylog2#13043 Closes: Graylog2#14901 Bug: elastic/elasticsearch#19443
teapot9
added a commit
to teapot9/graylog2-server
that referenced
this issue
Jul 11, 2023
Elasticsearch does not allow "." characters in field names since version 2.0. Support has been restored since version 5.0. For compatibility, graylog replaces "." with "_". However, when Elasticsearch >= 5.0 is used, this is unnecessary. For instance, Wazuh Indexer from the Wazuh project is forked from Opensearch 1.3. The character replacement causes issues with Wazuh, as the Dashboard expects dots as separator in the field name. This adds the option `replace_dots_in_field_names` to revert this behavior and allow the use of ".". The replacement is enabled by default for compatibility with existing graylog configurations. The extractor configuration in the web interface has been modified to show a warning when the user inputs a "." in the "Key separator" field. Closes: Graylog2#4583 Closes: Graylog2#6588 Closes: Graylog2#13043 Closes: Graylog2#14901 Bug: elastic/elasticsearch#19443
9 tasks
javanna
added
the
Team:Search Foundations
Meta label for the Search Foundations team in Elasticsearch
label
Jul 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>enhancement
help wanted
adoptme
:Search Foundations/Mapping
Index mappings, including merging and defining field types
Team:Search Foundations
Meta label for the Search Foundations team in Elasticsearch
v5.0.0-beta1
The dots in fieldnames work for 5.0 was for dynamic fields and document parsing. But we still need to add support for specifying dots in fieldnames in mappings apis. This is less troublesome to users as dynamic mappings (where sometimes the source field name cannot be controlled), but still a pain to deal with.
The text was updated successfully, but these errors were encountered: