Florian Bernd
Florian Bernd
Yes. This will be fixed in 8.12.1 by reverting the PR that broke it. In one of the 8.13.x patch releases I will reintroduce the (stored_fields) fix in a way...
Fixed in 8.12.1
Hi @R0boC0p, thanks for reporting! This is probably a specification issue where a property is incorrectly typed as "single or many" instead of just "array".
Duplicate of #7968
@JanToreKyrdalen The code generator is currently being reworked to address this and other issues. A rough estimation for completion is end of Q1 2024.
Currently blocked until https://github.com/elastic/elasticsearch-specification/issues/2545 is merged.
Implemented in 8.14.4
Hi @petr-horny-bsshop, 1. A conversion or inheritance structure like in NEST (where the descriptors are derived from the request/data classes or implement the same interface) won't get implemented in version...
Hey @baveryt, could you please include the JSON payloads for the request (and response, if possible)? They should be included in the exception after calling `DisableDirectStreaming()` on your `ElasticSearchSettings` instance.
Thanks for the additional details! It indeed seems like building the query argument fails for some cases when the argument is a collection.