Skip to content

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

Merged
merged 5 commits into from
Aug 16, 2018

Conversation

talevy
Copy link
Contributor

@talevy talevy commented Aug 15, 2018

this PR creates client-side instances of the following actions:

  • DeleteAction
  • ForceMergeAction
  • ReadOnlyAction
  • RolloverAction
  • ShrinkAction

AllocateAction can be found here (#32853)

this PR creates client-side instances of the following actions:

- DeleteAction
- ForceMergeAction
- ReadOnlyAction
- RolloverAction
- ForceMergeAction

ShrinkAction and AllocateAction are done separately
@talevy talevy added the :Data Management/ILM+SLM Index and Snapshot lifecycle management label Aug 15, 2018
@talevy talevy requested review from dakrone and colings86 August 16, 2018 04:40
@talevy
Copy link
Contributor Author

talevy commented Aug 16, 2018

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

Copy link
Contributor

@colings86 colings86 left a 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)
Copy link
Contributor

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.

Copy link
Contributor

@colings86 colings86 left a 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}
*/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@talevy talevy merged commit 6281982 into elastic:index-lifecycle Aug 16, 2018
@talevy talevy deleted the ilm-protocol-more-actions branch August 16, 2018 15:48
jasontedor pushed a commit that referenced this pull request Aug 17, 2018
this PR creates client-side instances of the following actions:

- DeleteAction
- ForceMergeAction
- ReadOnlyAction
- RolloverAction
- ForceMergeAction

AllocateAction was done separately
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/ILM+SLM Index and Snapshot lifecycle management
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants