Support field exclusion in _source. #117
Closed
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
|
Created Jira ticket at: https://jira.spring.io/browse/DATAES-195 |
|
@nistvan86 Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
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.
Elasticsearch allows us to specify field level exclusions when creating a mapping. See: https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-source-field.html#include-exclude
This functionality allows us to create a so called "indexed but not stored" kind of document field. The @field annotation's existing store attribute is not equivalent with this.
Spring Data ES currently lacks this feature in the document annotations, It should be possible to enable it using a custom mapping configuration file however it would be more expressive to specify this on the @field annotation directly.
This pull request implements the described functionality.