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

$_internalListCollections should support multitenancy

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2024-12-09

      We are introducing a new aggregation stage called `$listClusterCatalog` that must support multitenancy, that is:

      • Every namespace returned must be prefixed with the proper tenant id.
      • Every database returned must be prefixed with the proper tenant id.
      • The aggregation stage should only return those collections belonging to the tenant id provided on the request.

      The `$listClusterCatalog` calls `$_internalListCollections` under the hood, which is the one in charge of fetching and processing all the collections that `$listClusterCatalog` will end up returning to the user.

       

      Note: even though the tenant id protocol will be soon ripped out under SPM-3963, we still need to support multitenancy to be able to backport the `$listClusterCatalog` to v8.0. 

       

            Assignee:
            silvia.surroca@mongodb.com Silvia Surroca
            Reporter:
            silvia.surroca@mongodb.com Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: