Add environment variable to skip repository initialization. #2878
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
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.
lazy intialization (which could probably only be done by a method interceptor on the repository proxy) is problematic in the reactive context, so we are not using this approach.
This PR adds the possibility to just skip the initialization of the data in Elasticsearch by setting the environment variable
SPRING_DATA_ELASTICSEARCH_SKIP_REPOSITORY_INIT=true.If an application needs to have the repository initialized when this property is set to
true, thecreateIndexAndMappingIfNeeded()from theSimple(Reactive)ElasticsearchRepositorymust be explicitly called before writing data with the repository.Closes #2876