This repository was archived by the owner on May 18, 2020. It is now read-only.
When no version is provided to the EmbeddedElastic.Builder AutoDetectElasticVersion tries to auto-detect the elasticsearch version #79
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
…ElasticVersion tries to auto-detect the elasticsearch version
Author
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Providing the elasticsearch version is a bit of a redundant step since it can be found in the filename of the elasticsearch client jar. With auto-detect you don't have to keep the jar and embedded-elastic in sync. Providing the version still works as before.
Tested with java 8 and 11.