[DOCS-2523] Note that new aggregation framework can drop the existing collection Created: 13/Jan/14 Updated: 11/Jan/17 Resolved: 15/Jan/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Alexander Komyagin | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 5 weeks ago |
| Description |
|
In 2.6 the new aggregation with $out collection specified will drop the $out collection if it already exists. There is a discussion about making a change in that behavior, but until it's sorted out we need to warn users so they don't choose their main collection as $out. |
| Comments |
| Comment by Githook User [ 15/Jan/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Kay Kim (Inactive) [ 15/Jan/14 ] |
|
Will close for now. But please feel free to reopen if you want us to perhaps emphasize more. |