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

Move dropDatabase logic from ShardingCatalogClient into ShardingCatalogManager

    • Type: Icon: Task Task
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Fully Compatible
    • Sharding 2018-01-01, Sharding 2018-01-15, Sharding 2018-01-29

      The bulk of the dropDatabase business logic currently sits in a function on the ShardingCatalogClient.
      As part of moving the dropDatabase command to the config server, we should move the business logic from the ShardingCatalogClient to the ShardingCatalogManager.

      Note, the ShardingCatalogClient hierarchy is:
      ShardingCatalogClient base class
      --> child class ShardingCatalogClientImpl (the real implementation)
      --> child class ShardingCatalogClientMock (has dummy methods)
      Moving the dropDatabase function will require deleting code from all three of these classes.
      Also note, moving the dropDatabase function will also require updating some unit tests.

            kaitlin.mahar@mongodb.com Kaitlin Mahar
            kaitlin.mahar@mongodb.com Kaitlin Mahar
            0 Vote for this issue
            2 Start watching this issue