Implement unsigned long numeric field #5275
Merged
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
Closed
stevejgordon
added a commit
that referenced
this pull request
Jan 20, 2021
stevejgordon
added a commit
that referenced
this pull request
Jan 25, 2021
* Implement unsigned long (#5275) * test fixup Co-authored-by: Steve Gordon <sgordon@hotmail.co.uk>
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.
Add support for mapping an unsigned_long field. There is an issue currently with any mapping where the
null_valueneeds to be provided. This is because we store that value in adouble?property and currently, this causes a mapper_parser_exception. This has been raised for the ES team in elastic/elasticsearch#67565Contributes #5198