Skip to content

ILM: move_to_step:: next_step(StepKey type) doesn't match Elastic API #883

Closed
@voron86

Description

@voron86

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?

Activity

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[/+] on Sep 18, 2024
l-trotta

l-trotta commented on Sep 23, 2024

@l-trotta
Contributor

Hello, thank for the report! Yes this is an error in the API specification used to produce the Java code, we'll fix it and regenerate the client code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area: SpecificationRelated to the API spec used to generate client codeCategory: BugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @voron86@l-trotta

      Issue actions

        ILM: move_to_step:: next_step(StepKey type) doesn't match Elastic API · Issue #883 · elastic/elasticsearch-java