Harmonize naming of Elasticsearch auto-configuration classes #20857
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.
This PR harmonizes the naming of Elasticsearch auto-configuration components by including Elasticsearch in class names.
I've found the current naming to be very inconvenient to work with, since searching for Elasticsearch related auto-configuration components by entering ElasticsearchConfiguration or ElasticsearchProperties in IDEA's doesn't return some of vital components like
RestClientAutoConfiguration
andRestClientProperties
- those two are especially harder to find this way since they're not in the same package as components that currently do have Elasticsearch in their name (org.springframework.boot.autoconfigure.elasticsearch.rest
vsorg.springframework.boot.autoconfigure.data.elasticsearch
).A good example of well-named (and therefore easily discoverable) auto-configuration components is
org.springframework.boot.autoconfigure.session
, where all components contain Session in their names.Additionally, one further point of harmonization (that I didn't apply to this PR yet) could be to move components from
org.springframework.boot.autoconfigure.elasticsearch.rest
to simplyorg.springframework.boot.autoconfigure.elasticsearch
- as reactive client components inorg.springframework.boot.autoconfigure.data.elasticsearch
aren't nested inrest
subpackage.