Split and merge at tenant boundaries support changing a tenant's config shard

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Split and merge should copy config data for the tenants being moved, and the new set of config data should be maintained by the recipient.

            Assignee:
            [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: