-
Notifications
You must be signed in to change notification settings - Fork 25.3k
migrate more actions to protocol.xpack #32892
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
migrate more actions to protocol.xpack #32892
Conversation
this PR creates client-side instances of the following actions: - DeleteAction - ForceMergeAction - ReadOnlyAction - RolloverAction - ForceMergeAction ShrinkAction and AllocateAction are done separately
hey all. I've requested review. but I guess this review should be pending the review for Allocate Action since I want that one to govern how the rest of these are brought into the client |
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.
Same comments as the allocate action PR but I think this is good otherwise so we can apply the same fixes to both PRs 😄
org.elasticsearch.protocol.xpack.indexlifecycle.RolloverAction::parse), | ||
new NamedXContentRegistry.Entry(org.elasticsearch.protocol.xpack.indexlifecycle.ShrinkAction.class, | ||
new ParseField(org.elasticsearch.protocol.xpack.indexlifecycle.ShrinkAction.NAME), | ||
org.elasticsearch.protocol.xpack.indexlifecycle.ShrinkAction::parse) |
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.
Same comment here as in the allocate action PR about needing a common categoryClass
for all the actions so we can deserialise them without knowing the exact action type and also same comment about moving the registration of the server side objects away from the client.
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
|
||
/** | ||
* Parent class for the client-side ilm actions for the {@link NamedXContentRegistry} | ||
*/ |
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.
Same comment as in http://github.com/elastic/elasticsearch/pull/32853
this PR creates client-side instances of the following actions: - DeleteAction - ForceMergeAction - ReadOnlyAction - RolloverAction - ForceMergeAction AllocateAction was done separately
this PR creates client-side instances of the following actions:
AllocateAction can be found here (#32853)