You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the Elasticsearch API spec, attributes action and name are optional for the next_step object.
next_step (Required, object)
Properties of next_step:
phase (Required, string) The name of the phase that contains the action you want to perform or resume.
action (Optional, string) The name action you want to perform or resume. Required if name used.
name (Optional, string) The name of the step to move to and execute. Required if action used.
But in java client the nextStep property has type StepKey where the action and name are mandatory:
@JsonpDeserializable
public class StepKey implements JsonpSerializable {
private final String action;
private final String name;
private final String phase;
...
Due to the issue we can not use ElasticsearchAsyncClient for manual ILM in our application.
Is it possible to fix the inconsistency?
The text was updated successfully, but these errors were encountered:
voron86
changed the title
ILM: move_to_step::StepKey type doesn't match Elastic API
ILM: move_to_step:: next_step(StepKey type) doesn't match Elastic API
Sep 18, 2024
According to the Elasticsearch API spec, attributes
action
andname
are optional for thenext_step
object.But in java client the
nextStep
property has typeStepKey
where theaction
andname
are mandatory:Due to the issue we can not use ElasticsearchAsyncClient for manual ILM in our application.
Is it possible to fix the inconsistency?
The text was updated successfully, but these errors were encountered: