- Order - say i give http://localhost:9200/index1,index2,index3?.....
Will it first execute the query in index1 and then index2 and then index3?
No, it executes in parallel on all shards that belong to index1, 2, and 3.
What is the reason behind this question?
In my case, multiple apps might be using same cluster. So is the following
Cluster Level Awareness - Handling Master Slave. Thus, clearly separating
ES doesn't have a notion of master slave cluster awareness. There are
primary and replica shards for read / write operations and there is an
elected master that handles cluster wide administration.
Index Level Awareness - Handling multiple apps as each entity will be a
separate index rather than each app as an index. This will help in
allocating proper primary shards for each index and scaling according to it.
Each application having its own index will allow you to tune the settings
for each application need, this is valid design option.
Routing - Handling organisation for apps
And routing can help you to keep data with a specific property within a
shard, this allows you to keep search requests limited to only a few shards
instead to all shards that belong to an index. Routing by organisation
seems like a good property to use (assuming that it more or less partitions
the data into even shards)
If 'ids' range is supported, I can add each organisation as an alias with
the ids filter and a routing value
On the id field no numeric range is supported, since it is a string, if you
want to query documents based on a numeric range you are free to add an
additional number based field which you can use to execute a range filter
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/groups/opt_out.