Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PutIndexTemplateRequest doesn't support allow_custom_routing attribute for dataStream object #881

Closed
voron86 opened this issue Sep 18, 2024 · 1 comment · Fixed by #887
Closed
Labels
Area: Specification Related to the API spec used to generate client code Category: Bug Something isn't working

Comments

@voron86
Copy link

voron86 commented Sep 18, 2024

Java API client version

8.15.1

Java version

kotlin 2.0

Elasticsearch Version

8.x

Problem description

To be able to use custom routing with data streams we need to be able to put an index template with the allow_custom_routing: true attribute in the data_stream object. We use Kotlin service to configure indexes and streams. Due to lack of the attribute support in ElasticsearchAsyncClient::PutIndexTemplateRequest we should use low level rest client for the operation what is a bit inconvenient.
Is it possible to add the attribute support?
BTW, I see it's already supported in the response data objects.

@l-trotta
Copy link
Contributor

Hello, thanks for reporting this! The allow_custom_routing parameter seems to be missing from the API specification used to produce the Java code. failure_store is missing too, on the same object. We'll fix it in the specification and regenerate the java client.

@l-trotta l-trotta added Area: Specification Related to the API spec used to generate client code Category: Bug Something isn't working labels Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Specification Related to the API spec used to generate client code Category: Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants