Sylvain Wallez

Time representation is still something we have to work on in this new client. This will definitely be improved in a future release.

Please write issue titles and descriptions in English (Google translate does a decent job for this). Also avoid pasting screenshots of code: some people cannot read them, and this prevents...

Thanks for your answer @jerryguowei

The missing fields were added in https://github.com/elastic/elasticsearch-java/pull/292 Regarding the unification of search and multisearch builders, this is a very valid point. This however requires some changes that will cause a...

> Would it be good for you? I'd like to limit the number of framework-related methods on API classes to the bare minimum, and I don't expect `serializeToString` to be...

Thanks for the suggestions @don-vip! `toString` has already been mentioned in https://github.com/elastic/elasticsearch-java/issues/97 and indeed is a useful addition. We'll add it in a future version by serializing the type to...

A few additional precisions regarding Cloud deployments (I was in the Cloud team for 4 years before joining Clients): * the `cluster_name` in `GET /` is the cluster id, with...

RestHighLevelClient and Java API client both use the RestClient for http protocol handling. So this protocol error is most probably caused by a difference in the configuration of the RestClient...

@elasticmachine ok to test

Elasticsearch High Level REST Client 7.16 has a compatibility mode that allows it to work with Elasticsearch 8.x. This has to be enabled in `io.confluent.connect.elasticsearch.ElasticsearchClient` (possibly from an additional setting...