[DOCS-8887] Comment on: "manual/aggregation.txt" Created: 28/Sep/16 Updated: 11/Jan/17 Resolved: 28/Sep/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Mongodb 3.2.8 upgraded from 2.4 on Compose with Mongoose. Location: https://docs.mongodb.com/manual/aggregation/ |
||
| Participants: | |
| Days since reply: | 7 years, 20 weeks ago |
| Description |
|
I am using MongoDB on Compose and I just performed an upgrade with their environment from 2.4 to 3.2.8. In doing a review of my application some grouping issues were found. What we seem to have found is that after the upgrade the order of some of the elements in some of the documents were changed (see example below), and this was causing a problem with the grouping. The grouping was being done on a sub-document like on $person.address for the example below. And the grouping was not combining the records where the ordering of the data did not match, even though the data itself matched. If I change the line in the grouping from $person.address to be something like: {street: $person.address.street, city: $person.address.city, state: $person.address.state}The grouping seems to start to work again. Thoughts? Source database: { } after the upgrade / import: } |
| Comments |
| Comment by Ravind Kumar (Inactive) [ 28/Sep/16 ] |
|
Hello, Thank you for filing a DOCS ticket. The Documentation project is primarily for addressing issues with the MongoDB documentation. While your question relates to aggregation, the specific issue you are referencing is likely better addressed by our free community support engineers in the MongoDB Google Group. As far as the ordering of the subdocument after import, JSON only preserves the order of array values - any other objects are generally unordered. So, while after import the subdocument order has changed, you could still access the subdocuments in the same way - address.state returns "state" in both the original and imported documents. This shouldn't make a difference in aggregation - without seeing your aggregation query its hard to say why something changed. It is possible that you are simply seeing the result of major changes in MongoDB's aggregation framework, given the number of versions jumped. I hope this is of some help to you - our community support engineers can likely provide a more detailed technical overview of the issue. I would recommend providing the aggregation query to them, redacting or renaming any sensitive information such as field names or values. If during the course of discussions it becomes apparent that documentation changes are needed to better clarify the subject matter, we would be happy to address that. Simply create a new DOCS ticket, linking to the thread in the user group. Thank you, |