The coordinate rewrite can skip searching shards when the query filters on@timestamp, event.ingested or the _tier field. We currently check for missing shards across all the indices that are the query is running
The coordinate rewrite can skip searching shards when the query filters on@timestamp, event.ingested or the _tier field. We currently check for missing shards across all the indices that are the query is running against however, some shards/indices might not play a role in the query at all ...
The following example is based on Elasticsearch version 5.x onwards. An index with two shards, each having one replica will be created with the name test_index1 PUT /test_index1?pretty { "settings":{ "number_of_shards":2, "number_of_replicas":1 }, "mappings":{ "properties":{ "tags...
The following example is based on Elasticsearch version 5.x onwards. An index with two shards, each having one replica will be created with the name test_index1 PUT /test_index1?pretty { "settings" : { "number_of_shards" : 2, "number_of_replicas" : 1 }, "mappings" : { "propertie...
I noticed that all the calls such as index, delete, create and so on, all specifically copy in to the RequestConverters.Params object the data for wait for active shards:parameters.withWaitForActiveShards()Bulk is the only converther that's missing it in org.elasticsearch.client.RequestConverte...
The following example is based on Elasticsearch version 5.x onwards. An index with two shards, each having one replica will be created with the name test_index1 PUT /test_index1?pretty { "settings":{ "number_of_shards":2, "number_of_replicas":1 ...
The following example is based on Elasticsearch version 5.x onwards. An index with two shards, each having one replica will be created with the name test_index1 PUT /test_index1?pretty { "settings":{ "number_of_shards":2, "number_of_replicas":1 ...