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

Make sure that dropDatabase, dropCollection and renameCollection on sharded cluster delete the config.queryAnalyzers doc for the collection being dropped or renamed

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.0-rc1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding NYC
    • Fully Compatible
    • v7.0
    • Sharding NYC 2023-04-03, Sharding NYC 2023-04-17, Sharding NYC 2023-05-01

      The sharding_ddl_util::removeQueryAnalyzerMetadataFromConfig() is currently only called in sharded collection path. So the dropDatabase command currently doesn't delete the config.queryAnalyzers docs for unsharded collections. There was a bug in the jstest added in SERVER-69150. It wasn't verifying the config.queryAnalyzers doc is deleted so we failed to catch that.

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: