Fix store null values implementation. #2841
Merged
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
sothawo
added a commit
to sothawo/spring-data-elasticsearch
that referenced
this pull request
Jan 31, 2024
Original Pull Request spring-projects#2841 Closes spring-projects#2839 (cherry picked from commit 0a1e205)
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.
The new Elasticsearch Java client did not keep null values when writing the data to Elasticsearch (the old client did). As Spring Data Elasticsearch only adds null valued fields that are explicitly marked to be stored this way this change broke the expected behaviour.
This PR changes the configuration of the object mapper used by the Elasticsearch client to write null values.
Closes #2839