Refactor the initial split policy for data in primary shard

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Catalog and Routing
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-79179 introduced a new initial split policy in order to specify the shard where the data will be stored, considering that, we could refactor things so we can express the new policy based in the other, we would need to pass a shard (or the primary shard) in the constructor, and we could remove the primary shard from the SplitPolicyParam type.

            Assignee:
            [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: