Hi, I have a large-ish data set that could grow beyond a 100M. I have queries to be executed for this index. I would like to have query filter data local to a shard being sent to that shard, so that I spend less time creating a filter and even lesser time matching it for a shard. If I do not do this, I will have to create a filter that will have to contain data for all 100M documents across all shards, and every shard will have to match documents against that filter for all documents that are not even belonging to that shard.
I plan to write a query filter using the IndexQueryParserModule plugin. However, in the QueryParserContent, I can only see the Index object which contains some details of the index, like the name, etc. I could not see any other details like the specific shard where this query will be executed. Is there a way to write shard aware query and filter parsers? If not, can I create as many indices as I want to create shards (since I already get the index name), and effectively create one shard per index (+1 for replica) and treat every index as if it were a shard? Is that too heavy or just non-compliant to the philosophy of ES? Please let me know, Thanks, Sandeep -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e8c09c18-4192-41ae-86e9-5d67723e5558%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
