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

The drop of a sharded collection should not trigger the check for the existence of invalid views

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • Affects Version/s: 6.0.3, 6.1.0-rc4, 6.2.0-rc2
    • Component/s: None
    • None
    • Fully Compatible
    • v6.2, v6.1, v6.0
    • Sharding EMEA 2022-12-12
    • 153

      SERVER-71085 introduced new logic in release 6.3 that may cause CollectionCatalog::lookupView() to be invoked within the context of a collName.drop() execution (and consecutively, to raise an InvalidViewDefinition exception in case corrupted data are detected).

      This behaviour goes against what was implemented in SERVER-42373 - and this is why SERVER-71085 also introduced a try/catch clause to not propagate such error (and make the needed deductions when it is detected).

      For collName.drop() to maintain the semantics established by SERVER-42373 in multiversion cluster, the try/catch clause needs to also be backported to previous release branches.

            Assignee:
            paolo.polato@mongodb.com Paolo Polato
            Reporter:
            paolo.polato@mongodb.com Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: