bq. I am trying to see how sharding can be employed to
improve the query performance by adding the route to a shard based on a
field in schema.xml.
This is actually straightforward, just create the collections with
implicit routing.
See the collections API for CREATE and the "Document Routing" se
We have two collections which are 21G and constantly growing. The index on
one of them is also 12G. I am trying to see how sharding can be employed to
improve the query performance by adding the route to a shard based on a
field in schema.xml. So I am trying to figure out how to split the
collectio
This seems like an "XY problem". _Why_ do you want to do this?
Has your collection outgrown one shard and you feel you have to
split it? Sharding should only be used when you can't host your
entire collection on a single replica and still get adequate performance.
When you do reach that point, the
