I thought multi valued field was not supported as routing field? You'll likely need to choose a single-valued stable property for routing and not a value that a field that a single document can have several different values for.
So have a look at your schema for other candidate single-valued routing fields. If you cannot find one, perhaps compositeID (i.e. hash-based) is better for you. Having 8 shards on CompositeID, you could easily go to 16 -> 32 -> 64 by splitting your existing shards. But also in that case you'd need to have some stable single-valued ID to route on if you want more efficient queries, not hitting all shards every time. https://solr.apache.org/guide/solr/latest/deployment-guide/solrcloud-shards-indexing.html Jan > 29. nov. 2023 kl. 14:41 skrev Saksham Gupta > <[email protected]>: > > one of the values of a > multivalued field is being used to decide the shard of the document.
