[SERVER-76443] Make sure that dropDatabase, dropCollection and renameCollection on replica set delete the config.queryAnalyzers doc for the collection being dropped or renamed Created: 23/Apr/23  Updated: 12/Dec/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Cheahuychou Mao Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Cluster Scalability
Participants:

 Description   

Currently, the config.queryAnalyzers document is only deleted upon dropCollection, dropDatabase or renameCollection on a sharded cluster since there isn't a way to atomically delete associated metadata for a collection atomically with the dropCollection, dropDatabase or renameCollection command (in the sharded cluster case, the deletion of config.queryAnalyzers document is performed by the sharding DDL coordinators along with other config metadata documents). 


Generated at Thu Feb 08 06:32:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.