Laura Trotta

there should be a new release before the end of next month, I'll ping you in case of an earlier release.

fixed in [8.13.3](https://github.com/elastic/elasticsearch-java/releases/tag/v8.13.3)

Hello, thank you for reporting this! Currently in the java client those two options are present as part of the `source` field: ``` esClient .search(s -> s .source(so -> so...

Here's why: the server accepts both the query parameters (`_source_excludes`, `_source_includes`), and the `source` nested structure in the body to define which fields to exclude from the response. They're equivalent,...

Hello! As stated in the [compatibility section](https://github.com/elastic/elasticsearch-java?tab=readme-ov-file#compatibility) of the Readme: > The Java client is forward compatible; meaning that the client supports communicating with greater or equal minor versions of...

Hello, thanks for reporting this! Seems like we're missing some fields in the [API specification](https://github.com/elastic/elasticsearch-specification) used to produce the Java code, we'll add them and regenerate the client code to...

same as https://github.com/elastic/elasticsearch-java/issues/700, https://github.com/elastic/elasticsearch-java/issues/680

Hello, thanks for the report! So, creating the mapping with the category context seems to work fine when creating the request using the java client builders: ``` esClient.indices().create(c ->c .index("test-category")...

Hello! This was recently fixed in the [API specification](https://github.com/elastic/elasticsearch-specification) used to produce the Java code with this [PR](https://github.com/elastic/elasticsearch-specification/pull/2513). Updating the client to a more recent version should solve the problem.

Hello! Thank you for reporting this, and sorry for the wait. The problem here is that the java clients defaults to sending `stored_fields` as an array, while the server seems...