Separate responsibilities in shardsvrCommitToShardLocalCatalog

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-03-17
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      
Currently, shardsvrCommitToShardLocalCatalog combines multiple responsibilities. To improve clarity and maintainability, we should split this command into separate _shardsvrCommitCreateDatabase and _shardsvrCommitDropDatabase commands, for example.

      Additionally, consider refactoring the ShardServerOpObserver logic to avoid unnecessary serialization and deserialization. Introducing separate onDatabaseMetadataUpdate methods for each sharding catalog DDL operation may be beneficial, even if it increases the number of methods in OpObserver.

            Assignee:
            Pol Pinol
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: