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

Move dropDatabase logic from ShardingCatalogClient into ShardingCatalogManager

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:

      Description

      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.

        Attachments

          Activity

            People

            Assignee:
            kaitlin.mahar Kaitlin Mahar
            Reporter:
            kaitlin.mahar Kaitlin Mahar
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: