Missing support for SearchApplication API

[nhajratw]

I just ran into a case where a client wants to use the Search Application API

There doesn't seem to be a way to deal with this via the SpringData Elasticsearch interface.

[sothawo]

Both the Search Application feature and the API are marked in the Elasticsearch documentation as beta, that might change at any time. I'm not sure if it would make sense to implement support for this.

But the real showstopper here is that:

This feature is available to all Elastic Cloud deployments.

This feature is also available to self-managed deployments when Elastic subscription requirements are satisfied. View the requirements for this feature under the Elastic Search section of the Elastic Stack subscriptions page.

This means that even if we implement code that would support that API, it cannot be tested, as the docker images from Elasticsearch that are used in the TestContainer setup do not meet the requirements. Calling the _application endpoint results in an error:

GET :9200/_application/search_application
HTTP/1.1 403 Forbidden
content-encoding: gzip
content-length: 199
content-type: application/json

{
  "error": {
    "reason": "Current license is non-compliant for search application. Current license is active basic license. This feature requires an active trial, platinum, or higher license.",
    "root_cause": [
      {
        "reason": "Current license is non-compliant for search application. Current license is active basic license. This feature requires an active trial, platinum, or higher license.",
        "type": "security_exception"
      }
    ],
    "type": "security_exception"
  },
  "status": 403
}