-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Failing to deserialize response for GetIndexAsync
#8205
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
Comments
Here's a repo (xunit):
works with 10000, but doesn't work with |
Hi @cguedel, thank yo for the reproducer 🙂 It seems like the type of |
@flobernd Are you sure this is fixed? From my repro it still fails and from https://github.com/elastic/elasticsearch-net/blob/main/src/Elastic.Clients.Elasticsearch/_Generated/Types/IndexManagement/MappingLimitSettingsNestedObjects.g.cs#L36 it looks like this is still an |
@cguedel Yes, I noticed as well. Something went wrong when generating the new client. The preprocessing of the specification was not completed. I'll push a follow up fix soon. |
Confirm that this is fixed in 8.13.15, thanks for the quick response! |
Elastic.Clients.Elasticsearch version: 8.13.13
Elasticsearch version: 8.6.2
.NET runtime version: 8.0
Operating system version: Windows 11, Linux
Description of the problem including expected versus actual behavior:
Failing to deserialize response from
GetIndexAsync
due tosettings.index.mapping.nested_fields.limit
being returned as a string from the server.Steps to reproduce:
settings.index.mapping.nested_fields.limit
tolong.MaxValue
(or 9223372036854775807)client.Indices.GetAsync("indexName")
Expected behavior
Expected to properly deserialize response
Provide
DebugInformation
(if relevant):Index settings excerpt as retrieved using
curl -X GET http://server:9200/index
:The text was updated successfully, but these errors were encountered: