Do not include 'tid' field in change collection entries

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • QE 2023-02-06
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Change collections are already per-tenant, so it is not necessary to include the 'tid' field in each entry.

      Also, if we include the 'tid' field in each entry, then the backup team has to do work to make targeted restores (which use a backup from one tenant id and restore to a different tenant id) update all the 'tid' values.

      CC rishab.joshi@mongodb.com , denis.grebennicov@mongodb.com 

            Assignee:
            Rishab Joshi (Inactive)
            Reporter:
            Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: