-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Aggregation Framework, Querying
-
Fully Compatible
-
ALL
-
-
Query 2017-03-27, Query 2017-04-17, Query 2017-05-08, Query 2017-05-29, Query 2017-06-19
-
(copied to CRM)
-
0
Simply renaming a field in a $project currently disqualifies it from index consideration. The database should track simple field name changes in order to preserve index options.
This is particularly relevant since SERVER-19153 has been implemented and views are being introduced. In addition to BI use cases, consider that views would allow for more compact field names be stored in the collection and then expanded out via the view definition (eg: fn -> firstname).
Implementation of this feature would allow for more flexibility in how logically equivalent aggregation pipelines are written while optimal performance is maintained.
- causes
-
SERVER-31696 Aggregation's renamed fields analysis is broken for dotted field paths, causes incorrect query results
- Closed
- is duplicated by
-
SERVER-31729 Views: index on underlying collection are not used if field is renamed by $project (first stage)
- Closed
- related to
-
SERVER-5477 when sharded, no need to merge groups if $group _id is the shard key or original document _id
- Backlog
-
SERVER-72037 Allow $replace(With|Root) to participate more in $match optimizations
- Closed