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

Investigate if we can get rid of assumes_no_implicit_collection_creation_after_drop tag

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing

      Currently, there are many tests skipping the suites that implicitly create sharded collections (like this one) just because they are checking if the collection exists after a drop.
      These tests fail in this kind of suite because we implicitly recreate the collection on a drop to make sure it is a sharded collection.

      The tests with the described behavior are tagged with assumes_no_implicit_collection_creation_after_drop.

      The aim is to eventually enable the tests that are not running on those suites that implicitly create sharded collections just because they are checking if the collection exists after a drop.

            Assignee:
            Unassigned Unassigned
            Reporter:
            silvia.surroca@mongodb.com Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: