[SERVER-14193] deprecate (JS) group command Created: 06/Jun/14 Updated: 29/Aug/17 Resolved: 10/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MapReduce |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.6 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | David Storch |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||
| Sprint: | Query 14 (05/13/16) | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Description |
|
Now that aggregation framework ought to be used for pretty much all groupings, it doesn't make sense to leave group as is - it creates a lot of confusion in users' minds - they assume group is part of aggregation framework and then assume all the limits that group has applies to all aggregations. We plan to remove/hide it in 3.6 and start warnings about it being deprecated in 3.4. |
| Comments |
| Comment by Githook User [ 10/May/16 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |