[DOCS-12607] Docs for SERVER-39663: db.collection.dropIndex() should not accept multiple index names Created: 09/Apr/19  Updated: 13/Nov/23  Resolved: 10/Apr/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.10, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-39663 db.collection.dropIndex() should not ... Closed
Participants:
Days since reply: 4 years, 44 weeks ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

The documentation is ambiguous in whether db.collection.dropIndex() can accept the "" wildcard to drop all indexes. We should probably add a note somewhere that it isn't allowed as it may drop multiple indexes if more than one exist. Users wanting to use the "" wildcard to drop all indexes should be referred to db.collection.dropIndexes() instead.

Engineering Ticket Description:

We extended the dropIndexes command in SERVER-37727 to accept an array of index names. As a result, the db.collection.dropIndex() shell helper, which is built on the dropIndexes command, now accepts multiple index names. It would be less confusing for users if we added some validation to this shell helper to reject '*' and arrays of index names.

Scope of changes

  • source/reference/method/db.collection.dropIndex.txt
  • source/release-notes/4.2-compatibility.txt

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 10/Apr/19 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'Kay Kim', 'username': 'kay-kim'}

Message: DOCS-12607: dropIndex() and '*'
Branch: master
https://github.com/mongodb/docs/commit/f29f32c60556da0801e64affd043404cdfc057d5

Generated at Thu Feb 08 08:05:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.