Document special behaviour of ignore_malformed for geo_point mappings #125692
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
craigtaverner
added
>docs
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
colleenmcginnis
requested review from
leemthompo
and removed request for
colleenmcginnis
iverase
approved these changes
Apr 3, 2025
💚 Backport successful
|
craigtaverner
added a commit
to craigtaverner/elasticsearch
that referenced
this pull request
Apr 7, 2025
…elastic#125692) With `geo_point` fields, here is the special case of values that have a syntactically valid format, but the numerical values for `latitude` and `longitude` are out of range. If `ignore_malformed` is `false`, an exception will be thrown as usual. But if it is `true`, the document will be indexed correctly, by normalizing the latitude and longitude values into the valid range. The special `_ignored` field will not be set. The original source document will remain as before, but indexed values, doc-values and stored fields will all be normalized.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Apr 7, 2025
…#125692) (#126384) With `geo_point` fields, here is the special case of values that have a syntactically valid format, but the numerical values for `latitude` and `longitude` are out of range. If `ignore_malformed` is `false`, an exception will be thrown as usual. But if it is `true`, the document will be indexed correctly, by normalizing the latitude and longitude values into the valid range. The special `_ignored` field will not be set. The original source document will remain as before, but indexed values, doc-values and stored fields will all be normalized.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With
geo_pointfields, here is the special case of values that have a syntactically valid format, but the numerical values forlatitudeandlongitudeare out of range.If
ignore_malformedisfalse, an exception will be thrown as usual. But if it istrue, the document will be indexed correctly, by normalizing the latitude and longitude values into the valid range. The special_ignoredfield will not be set. The original source document will remain as before, but indexed values, doc-values and stored fields will all be normalized.Fixes #94807
This PR also adds a bunch of line-breaks to the geo-point.md file to make it easier to back-port this change to the 8.x branch. The line breaks have been chosen to mimic the original ASCIIDOC files, so the diff will be cleaner.