Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-70741

The "tid" field is projected out when reading from change collections

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • QE 2022-10-31

      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.

            Assignee:
            rishab.joshi@mongodb.com Rishab Joshi (Inactive)
            Reporter:
            janna.golden@mongodb.com Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: