Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-15797

Remove deprecated note for collection.drop()

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 6.0.4, 5.0.15
    • None
    • manual, Server
    • None

    Description

      In the collection.drop() documentation we still have a note saying:

      For a sharded cluster, if you use db.collection.drop() and then create a new collection with the same name, you must either:

      Running flushRouterConfig after collection drop it is not necessary anymore starting from 5.0. In fact this note have been introduced in DOCS-13703 due to SERVER-17397 that was fixed in 5.0

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. DOCS-15799 Starting from 5.0 there is no need to run dropDatabase multiple times

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17397 Dropping a Database or Collection in a Sharded Cluster may not fully succeed

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. DOCS-13703 drop collection in sharded environments should point out that all mongos instances need cache refreshed

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              ian.fogelman@mongodb.com Ian Fogelman
              tommaso.tocci@mongodb.com Tommaso Tocci
              Githook User Githook User
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                10 weeks, 4 days ago