Put Lifecycle method in ILM Client causes 400 Bad Request

The PUT Lifecycle Endpoint send the name as a property in the body, which is not accepted by Elasticsearch. This causes a 400 Bad Request Response. Therefore this method is not usable.

Code

Application

client.ilm().putLifecycle(it -> {
    it.name(policy.name())
    it.policy(policy)
});

Request

Endpoint: PUT /_ilm/policy/{id}

{
  "policy": {
    "phases": {...},
    "name": "{id}"
  }
}

Response

Status: 400 Bad Request

{
  "error": {
    "root_cause": [
      {
        "type": "x_content_parse_exception",
        "reason": "[1:94] [lifecycle_policy] unknown field [name]"
      }
    ],
    "type": "x_content_parse_exception",
    "reason": "[1:101] [put_lifecycle_request] failed to parse field [policy]",
    "caused_by": {
      "type": "x_content_parse_exception",
      "reason": "[1:94] [lifecycle_policy] unknown field [name]"
    }
  },
  "status": 400
}

[swallez]

@oliverlockwood I’m working on a number of things both on the Java client and other projects, and prioritizing something will make some people happy but will obviously not be satisfying for others who don’t care much about it. I understand your concerns and I’m currently actively working on fixing the data structure related issues (coming from the API specification) since they’re more problematic that say missing features or a more extensive documentation, which are also highly requested. However data structure related issues also have to be prioritized according to the usage frequency of the affected APIs.

Now I heard you, and expect some news on these issues very soon. Thanks.

I also added a comment in #203 about the split package issue.

[swallez]

This has been fixed in PR #292, backported to version 8.2 in PR #293 and to version 7.17 in PR #294.