[SERVER-72835] Do not include 'tid' field in change collection entries Created: 13/Jan/23  Updated: 24/Jan/23  Resolved: 24/Jan/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Rishab Joshi (Inactive)
Resolution: Won't Do Votes: 0
Labels: change-streams-support, phase2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Initiative
Sprint: QE 2023-02-06
Participants:

 Description   

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 


Generated at Thu Feb 08 06:22:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.