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

Missing Settings "index.allocation.max_retries" #8461

Closed
TheFireCookie opened this issue Feb 26, 2025 · 3 comments
Closed

Missing Settings "index.allocation.max_retries" #8461

TheFireCookie opened this issue Feb 26, 2025 · 3 comments

Comments

@TheFireCookie
Copy link
Contributor

TheFireCookie commented Feb 26, 2025

Elastic.Clients.Elasticsearch version:
8.17.1
Elasticsearch version:
8.16.0
.NET runtime version:
8.0.11
Operating system version:
Rocky Linux 9

Description of the problem including expected versus actual behavior:
A clear and concise description of what the bug is.

Steps to reproduce:

  1. Try to map the index.allocation.max_retires
  2. Field is not available in the generated API reference

Map it by hand:

Image

Expected behavior
Mapped in the C# classes

Image

Provide ConnectionSettings (if relevant):

Provide DebugInformation (if relevant):

@TheFireCookie TheFireCookie added 8.x Relates to 8.x client version Category: Bug labels Feb 26, 2025
@flobernd
Copy link
Member

Hi @TheFireCookie, yes the IndexSettings type currently does not contain a dedicated property for each setting.

Is there a particular reason why the OtherSettings do not work for you in this case? Or is this issue just meant as an enhancement request?

@TheFireCookie
Copy link
Contributor Author

Hi, thanks for the fast answer. It's just an enhancement request. You can close the issue if it's accepted to do it with the other settings. I'm not blocked at all

Copy link
Contributor

github-actions bot commented Mar 4, 2025

This issue is stale because it has been open 5 days with no activity. Remove stale label or comment or this will be closed in 2 days.

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

No branches or pull requests

2 participants