Support different routing for each id in multiget

[mateog5]

Multiget doesn't support different routing for each id

public Flux<MultiGetItem> multiGet(Query query, Class clazz, IndexCoordinates index)
-->
private List<MultiGetRequest.Item> getMultiRequestItems(Query searchQuery, Class<?> clazz, IndexCoordinates index)

for (String id : searchQuery.getIds()) {
   MultiGetRequest.Item item = new MultiGetRequest.Item(indexName, id);

  if (searchQuery.getRoute() != null) {
	item = item.routing(searchQuery.getRoute());
  }
....

Currently is only possible to set same routing for all ids

GET index-search/_mget
{
"docs": [
{
"_type": "_doc",
"_id": "xxxx",
"routing": "routingForXXXX, routingForYYYY"
},
{
"_type": "_doc",
"_id": "yyyy",
"routing": "routingForXXXX, routingForYYYY"

}

]
}

Should be possible to set different routing for each id

GET index-search/_mget
{
"docs": [
{
"_type": "_doc",
"_id": "xxxx",
"routing": "routingForXXX"
},
{
"_type": "_doc",
"_id": "yyyy",
"routing": "routingForYYYY"

}

]
}

[sothawo]

For this we need to introduce something like a IdWithRouting which contains an id and a routing value and add the possibility to set these on a Query. When building the request these values can then be used to build the get request with different routing values for the ids.

[frnandu]

I'm also needing this for our project, so +1 for quick implementation

[sothawo]

implemented it and added a helper method to create the query:

Query query = Query.multiGetQueryWithRouting(
  Arrays.asList(
    new Query.IdWithRouting(ID_1, ROUTING_1),
    new Query.IdWithRouting(ID_2, ROUTING_2),
    new Query.IdWithRouting(ID_3, ROUTING_3)
    )
);

List<MultiGetItem<RoutingEntity>> multiGetItems = operations.multiGet(query, RoutingEntity.class);