Update recipient state machine depending on featureFlagSliceMerge

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.2.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Server Serverless 2021-09-27, Server Serverless 2021-10-04, Server Serverless 2021-10-11, Server Serverless 2021-10-18, Server Serverless 2021-10-25, Server Serverless 2021-11-01, Server Serverless 2021-11-15
    • 182
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Add a "protocol" field with a string value of either "multitenant migration" or "slice merge". We initially choose a protocol based on whether slice merge is enabled (see above), then persist this choice in the state machine and use the state machine to determine the protocol in later steps.
      Make tenant id optional (if Merge is enabled it must be absent, otherwise it must be a string).

      UPDATE: This ticket does the following things.
      1) Update donor state machine depending on featureFlagSliceMerge (SERVER-59494)
      2) Update recipient state machine depending on featureFlagSliceMerge (SERVER-59495)
      3) Add protocol & tenant id optional in recipientSyncData command. (SERVER-59787)

            Assignee:
            Suganthi Mani
            Reporter:
            A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: