Open oli-tu opened 2 years ago
Any info about that?
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 (limited) breaking change because of the class structure change. I've opened https://github.com/elastic/elasticsearch-specification/issues/1726 to address this.
@adrian-arapiles how did you proceed with this structure? Did you seperately create search and multisearch requests?
@adrian-arapiles how did you proceed with this structure? Did you seperately create search and multisearch requests?
Hi @Erkanerkisi, in my case I was migrating from the old client to this new client, so I still leave old client in methods that uses multisearch request until this ticket has been implemented
I feel a little sad with that because the old client is already deprecated but the new client hasn't yet same features than old client. It's a little confusing for me.
@adrian-arapiles yea same situation applies us, we're using search requests and multisearch requests in a way that are replaceable each other. putting search requests in a multisearch structure is crutial from our side. But this way, we have to seperate them.
The former Java High Level client had the nice feature, that single _search requests and the items of _msearch request were compatible, so our application could use the same builder for both, single and bulk searches. Although not in the specification, the msearch request code also supported source_include/excludes and the collapse parameter for msearches.
The new Elastic client, while forcefully implementing the spec, splits single and bulk searches into two worlds, including the deficiencies of the msearch endpoint described here.
While attempting to migrate to the new client two major pain points came up:
I created example queries for the old and new client, comparing single and msearchs. See my TODOs for the missing compatibilites. Is there any implementation planned? Is there any workaround for it?
Old Highlevel client
New elasticsearch-java