[SERVER-20969] Enforce restriction that $indexStats is the first pipeline stage Created: 16/Oct/15  Updated: 04/Nov/15  Resolved: 28/Oct/15

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Index Maintenance
Affects Version/s: 3.2.0-rc0
Fix Version/s: 3.2.0-rc2

Type: Improvement Priority: Minor - P4
Reporter: Jeffrey Yemin Assignee: James Wahlin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Minor Change
Participants:

 Description   

Currently the aggregation framework does not enforce any restrictions on the position of the new $indexStats stage within the aggregation pipeline. Since there are currently no uses cases for $indexStats being anything but the first stage in the pipeline, it may make sense for the server to report an error if it's not the first stage.

This is similar to what is done with $out, which is currently required to be the last stage in the pipeline.

We can always relax the restriction in the future if new stages are added which make sense to go before $indexStats



 Comments   
Comment by Githook User [ 28/Oct/15 ]

Author:

{u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}

Message: SERVER-20969 Restrict $indexStats to first pipeline stage
Branch: master
https://github.com/mongodb/mongo/commit/97da4befad629f5cff05851c539ae88a4127d8f8

Comment by Charlie Swanson [ 16/Oct/15 ]

Seems reasonable, and easy enough. Scheduling for 3.1 Required. james.wahlin, if you don't have time for this in the coming iteration or two, feel free to assign to me.

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