When using a custom preference key in searches, ES ends up querying all the N shards of the index right? Surely out of N, few will be replicas, few will be primary
How does ES achieve this just using the string we pass? Does it store the preference in some cluster state for future reference so that same set of shards will be picked or is it computed in some deterministic manner (obviously)
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.