[SERVER-6023] add an explicit requireOrder argument to NamespaceDetailsTransient::getCursor() Created: 07/Jun/12  Updated: 11/Jul/16  Resolved: 07/Jun/12

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 2.1.2

Type: Improvement Priority: Major - P3
Reporter: Aaron Staple Assignee: Aaron Staple
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-5090 aggregation: use covered index Closed
Participants:

 Description   

The following assumption makes it difficult for NamespaceDetailsTransient::getCursor() to be used for index only projection by clients other than the query implementation.

        /** If no ParsedQuery was supplied, it's assumed no reordering will be applied. */
        bool requireOrder() const { return !_parsedQuery; }

It is straightforward to replace this with an additional argument to NamespaceDetailsTransient::getCursor().



 Comments   
Comment by auto [ 07/Jun/12 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-6023 Add an explicit requireOrder argument to NamespaceDetailsTransient::getCursor().
Branch: master
https://github.com/mongodb/mongo/commit/753c001845de3e51d007f99dce20ae5a04fa11d9

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