[SERVER-18622] listCollections command should special-case filtering by name. Created: 21/May/15  Updated: 17/May/19  Resolved: 13/Oct/15

Status: Closed
Project: Core Server
Component/s: Performance, Storage
Affects Version/s: None
Fix Version/s: 3.2.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Charlie Swanson
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-8976 listCollections command should specia... Closed
Related
is related to SERVER-18624 listCollections command should not be... Closed
Backwards Compatibility: Major Change
Sprint: QuInt A (10/12/15), QuInt B (11/02/15)
Participants:

 Description   

Currently it does all the work for all collections in a namespace, and throws out results from non-matching namespaces.



 Comments   
Comment by Charlie Swanson [ 13/Oct/15 ]

Note that this change affects the behavior of the listCollections command. The result is no longer sorted alphabetically by collection name. There are no guarantees on the sort order. The shell helper db.getCollectionInfos(), however, remains sorted alphabetically.

Comment by Githook User [ 13/Oct/15 ]

Author:

{u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}

Message: SERVER-18622 listCollections should special case filtering by name

Note that the listCollections command is no longer guaranteed to return the
collections in alphabetical order by name. The shell helper will still do so.
Branch: master
https://github.com/mongodb/mongo/commit/6abdb820a8259591cc43ad4ed52dbf7c3509d04b

Generated at Thu Feb 08 03:48:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.