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

Move dropCollection logic from ShardingCatalogClient into ShardingCatalogManager

    XMLWordPrintable

    Details

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

      Description

      The bulk of the dropCollection business logic currently sits in a function on the ShardingCatalogClient.

      As part of moving the dropCollection 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 implemenation)
      --> child class ShardingCatalogClientMock (has dummy methods)

      Moving the dropCollection function will require deleting code from all three of these classes.

      Also note, moving the dropCollection function will also require updating some unit tests.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: