Florian Bernd

Hi @jmisaxobank , I was on leave for quite a while and didn't have time to work on this issue yet. It's on my list and not forgotten 🙂 8.19.x...

@jmisaxobank Could you please send me the JSON **response** of one of the failing operations? I could use that as a reproducer, which would speed up validation of my proposed...

Thank you @jmisaxobank . The root cause of the problem seems to be an incorrect type in the specification. I created [this PR](https://github.com/elastic/elasticsearch-specification/pull/5108) to solve the issue. Usability of this...

@jmisaxobank Fixed in 8.19.1 / 9.1.1. I as well eliminated the union for better usability.

@jmisaxobank That's unexpected. I'll check again tomorrow.

@jmisaxobank There was another type problem in the Elasticsearch specification. I created a PR and will release a new version of the client shortly after it gets merged 🙂

Should finally be fixed now in 8.19.3 / 9.1.4.

Some endpoints require multiple indices to be sent as a comma separated list, like e.g. - https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html#docs-reindex-api-request Other ones only accept arrays, like e.g.: - https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-aliases.html We must model these...

@cguedel The preferred solution affects all language clients (as it must be fixed in the specification) and requires careful planning. We had an initial brainstorming regarding this issue, but large...

@Bhavyagc02 There have been a few breaking changes regarding to aggregations in 8.13. These are documented in the [release notes](https://github.com/elastic/elasticsearch-net/releases/tag/8.13.0). Please let me know if you need further assistance after...