Allow reshardCollection() to not require the hashed index for hashed shard keys

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • Cluster Scalability 2024-07-22, Cluster Scalability 2024-08-19, Cluster Scalability 2024-09-02
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Given that we can drop the hashed index, it means we also don't have to require it in the first place when someone is sharding a collection with a hashed shard key.

      Today, people have to build the hashed index, shard the collection, then drop the hashed index. Building an extra index not only takes time, but also impacts your workload, both the index building itself and the existence of an extra index even if temporary.

      So let's not require it in the first place for hashed shard keys.

              Assignee:
              Cheahuychou Mao
              Reporter:
              Garaudy Etienne
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: