[SERVER-70741] The "tid" field is projected out when reading from change collections Created: 20/Oct/22 Updated: 29/Oct/23 Resolved: 26/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Rishab Joshi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | QE 2022-10-31 | ||||||||
| Participants: | |||||||||
| Description |
|
It looks like the "tid" field isn't in the list of fields to include in the output doc when reading from change collections. Specifically, it looks like the field is filtered out here. This means there will never be a "tid" field when constructing the NamespaceString object. I hit this when attempting to add an assertion in NamespaceStringUtil::deserialize that a tenantId is always set when multitenancySupport and featureFlagRequireTenantId are enabled running multitenant_read_from_change_collection and basic_read_from_change_collection.js. |
| Comments |
| Comment by Githook User [ 26/Oct/22 ] |
|
Author: {'name': 'Rishab Joshi', 'email': 'rishab.joshi@mongodb.com', 'username': 'rishvin'}Message: |