Investigate consequences of directly renaming a bucket namespace in a sharded cluster

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The _shardsvrRenameCollection command and the rename coordinator don't seem to explicitly check for bucket namespaces.

      Purpose of this ticket is to double check if it's fine for the user to directly invoke rename operations on bucket namespaces or if we should rather disallow it, always requiring to invoke rename on the view in case of timeseries.

      At first glance, it should not be problematic to directly address the bucket namespace because the DDL locks are acquired on the right namespace and the coordinator works on the right namespace as well (since the translation should be a no-op).

            Assignee:
            Unassigned
            Reporter:
            Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: