Replacement updates should preserve the cluster key

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Replacement updates on clustered collections currently assume _id as the cluster key. Extend the logic to support arbitrary cluster keys.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Josef Ahmad
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: