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

Tenant migration access blocker registry to use TenantId object for Shard Split

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Server Serverless 2022-12-12, Server Serverless 2022-12-26

    Description

      Change the tenant_migration_access_blocker_util and the tenant_migration_access_blocker_registry to use a vector<tenant_id> instead of the vector<string> and all other places where we use StringData instead of a TenantId object. The unit tests should also be changed. In case of this ticket done asynchronously we should have support for both TenantId object and StringData until the other tickets are done. We can either mark the change blocked + depend on; or we can create a TODO ticket to delete the old api still using StringData over TenantId.

      We should also identify and create a TODO ticket (SERVER-71669) as part of this work to identify any place that will be left still using a StringData for backward compatibility with MTM and Shard Merge (since both protocol are still using a StringData type).

      We cannot fully modify the TenantMigrationAccessBlockerRegistry until all migration protocol are moved to use TenantId, therefor SERVER-71673 was created to handle the refactoring to only use TenantId.

      Attachments

        Activity

          People

            mathis.bessa@mongodb.com Mathis Bessa
            mathis.bessa@mongodb.com Mathis Bessa
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: