Elasticsearch Java Client: Support for custom mappings/settings

Custom plugins sometimes require custom mappings/settings.
As an example, elastiknn requires a specific setting to enable the plugin for a given index and a custom field mapping for the configuration.

With the Rest High-Level Client, this can be done using XContentFactory. The new Elasticsearch Java Client is much more elegant and type-safe but it does not seem to support custom settings/mappings.

Is there any plan to support this?


Yes, definitely. We've done some prototyping on this already which is captured in [roadmap] Add support for plugin-defined custom components · Issue #252 · elastic/elasticsearch-java · GitHub

Please subscribe to that issue to follow its progress. Feedback is of course welcome!

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.