Add Criteria example for nested Elasticsearch field #705
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.
Relates to #591.
This PR adds a small Spring Data Elasticsearch example that demonstrates using
org.springframework.data.elasticsearch.core.query.Criteriaagainst a nested field.Changes:
Talkdocument with aspeakersfield annotated as@Field(type = FieldType.Nested).Speakervalue object.ElasticsearchOperationsTestwithcriteriaQueryOnNestedSpeakers(), which:Talkwith a nestedSpeaker,Talkwithout speakers,CriteriaQueryonspeakers.name,Note:
On my local machine, the existing
ElasticsearchOperationsTestfails to start theApplicationContext with a
DataAccessResourceFailureExceptionwhen initializingConferenceRepository:status: 400, [es/indices.exists] Expecting a response body, but none was sent.This also happens on a clean checkout of
main.The changes in this PR are limited to adding the nested Criteria example and do not modify
the existing Elasticsearch configuration.