-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Remove IndexNameExpressionResolver from base transport classes that don't use it #120531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove IndexNameExpressionResolver from base transport classes that don't use it #120531
Conversation
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
| protected final ThreadPool threadPool; | ||
| protected final TransportService transportService; | ||
| protected final ClusterService clusterService; | ||
| protected final IndexNameExpressionResolver indexNameExpressionResolver; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
boom
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM; I'd like this to be backported to 8.x too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM2, nice cleanup!
💔 Backport failed
You can use sqren/backport to manually backport by running |
Follow-up to elastic#120531 to remove all the now-redundant constructor parameters.
Follow-up to #120531 to remove all the now-redundant constructor parameters.
Follow-up to elastic#120531 to remove all the now-redundant constructor parameters.
Follow-up to elastic#120531 to remove all the now-redundant constructor parameters. Backport of elastic#123258 to 8.x
) Follow-up to #120531 to remove all the now-redundant constructor parameters.
IndexNameExpressionResolveris needed byTransportMasterNodeAction, even though it doesn't use it. This removesIndexNameExpressionResolverfrom that base class, moving the field into classes that actually use it.Note that the majority of these changes were automated remove-parameter refactorings.
There are many classes that still have
IndexNameExpressionResolverin their injection constructor that doesn't go anywhere - these can be removed as part of this PR (once the concept is approved), or later over time.