Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
Query Optimization
-
Minor Change
Description
Right now the only way to return documents in natural order is to use a collection scan cursor (not an index cursor). And, currently, if both an index hint and natural ordering are specified for a query, the hint will supersede the natural ordering spec and the results will not be returned in natural order. Instead, hinting an index that cannot be used to retrieve results in natural order should produce an error.
Test
c = db.c;
|
c.drop();
|
c.ensureIndex( { a:1 } );
|
c.save( { a:2 } );
|
c.save( { a:1 } );
|
|
|
printjson( c.find( { a:{ $gt:0 } } ).sort( { $natural:1 } ).hint( { a:1 } ).toArray() );
|
printjson( c.find( { a:{ $gt:0 } } ).sort( { $natural:1 } ).hint( { a:1 } ).explain() );
|
Attachments
Issue Links
- is duplicated by
-
SERVER-8561 Query with sort ($natural:1) is reported as indexOnly when it should not be
-
- Closed
-
- related to
-
-
- Closed
-
-
SERVER-8607 add support for natural order sorting in memory
-
- Closed
-