Consider moving sharding catalog metadata writes to ShardingCatalogManager

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      File src/mongo/db/global_catalog/ddl/sharding_catalog_manager.h contained an unresolved TODO comment without an attached Jira ticket here:

      TODO: Currently the code responsible for writing the sharding catalog metadata is split between
      this class and ShardingCatalogClient. Eventually all methods that write catalog data should be
      moved out of ShardingCatalogClient and into this class.
      

      This TODO comment prevents modifying the entire file, because the code linter in Evergreen fails for all TODO comments not referencing Jira tickets.
      To make the linter pass, I am now opening this ticket and assigning it to CAR.
      I cannot estimate the feasibility and necessity of the proposed change. Feel free to close and remove the TODO if it has become irrelevant.

            Assignee:
            Unassigned
            Reporter:
            Jan Steemann
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: