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

Allow the `restore` role to do all DDL on time-series buckets.

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • Execution Team 2024-02-19

      The server forbids some DDL operations, like shardCollection and drop, on time-series buckets collections. For most applications this is sensible, but it prevents mongosync from sending a `collectionUUID` when doing these operations.

      For now that's OK because mongosync only does single-threaded DDL; however, as of REP-2924 mongosync will augment preexisting namespaces, which means we'll potentially have multiple mongosyncs syncing to the same collection.

      Unless we're going to disavow data integrity for time-series in these situations, then, the server will need to allow mongosync to do full DDL on time-series bucket collections. These operations should all accept `collectionUUID` as well.

      I envision that, as with SERVER-77003, the server will only allow this functionality to clients with the `restore` role.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            felipe.gasper@mongodb.com Felipe Gasper
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: