Fix typo when assigning null_value in GeoPointFieldMapper #49645
Conversation
This file contains 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
It seems that code was pasted but not fully changed
csoulios
added
the
:Analytics/Geo
|
Pinging @elastic/es-analytics-geo (:Analytics/Geo) |
iverase
approved these changes
Nov 27, 2019
|
@elasticmachine run elasticsearch-ci/default-distro |
|
+1 for a test |
|
Test is coming :) |
csoulios
added a commit
that referenced
this pull request
Nov 27, 2019
Backport of #49645 to 7.x This PR fixes a trivial typo error that affects assigning null_value in the GeoPointFieldMapper
This was referenced Feb 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes a trivial typo error that affects assigning
null_valuein theGeoPointFieldMapperIt seems that code was pasted from the line above but not fully changed.