[SERVER-12015] Reenable use of covering indexes with aggregation Created: 09/Dec/13  Updated: 03/May/17  Resolved: 27/Aug/15

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Performance, Querying
Affects Version/s: 2.5.5
Fix Version/s: 3.1.8

Type: Improvement Priority: Critical - P2
Reporter: Mathias Stearn Assignee: Charlie Swanson
Resolution: Done Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-9011 Reenable use of covering indexes with... Closed
Duplicate
is duplicated by SERVER-15026 Allow covered queries for first stage... Closed
is duplicated by SERVER-16388 Aggregation operation not using any f... Closed
is duplicated by SERVER-22912 Query Optimizer Closed
Related
related to SERVER-11831 Use documentFromBsonWithDeps in agg a... Closed
Backwards Compatibility: Fully Compatible
Sprint: Quint Iteration 7, QuInt 8 08/28/15
Participants:

 Description   

It is not currently possible to use covered indexes with the new query framework without using the full projection code in the non-covered cases.



 Comments   
Comment by Githook User [ 27/Aug/15 ]

Author:

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

Message: SERVER-12015 Re-enable use of covering indices in an aggregation pipeline
Branch: master
https://github.com/mongodb/mongo/commit/843fd8ae34d06ed73f824c124cd2d9ef7d23b814

Comment by Githook User [ 19/Dec/13 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-11831 Use documentFromBsonWithDeps in agg again

This bypasses new query framework projection and replaces it with a much faster
dedicated code path. The downside is that it prevents using covering indexes
in the cases where that was allowed (SERVER-12015).
Branch: master
https://github.com/mongodb/mongo/commit/3e707bcd22b7c0e8275d25bf8e8b28c3cec4cc67

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