Details
-
Bug
-
Resolution: Cannot Reproduce
-
Major - P3
-
None
-
None
-
Mongodb 3.2.8 upgraded from 2.4 on Compose with Mongoose.
*Location*: https://docs.mongodb.com/manual/aggregation/
*User-Agent*: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36
*Referrer*: https://www.mongodb.com/contact
*Screen Resolution*: 2400 x 1350
Mongodb 3.2.8 upgraded from 2.4 on Compose with Mongoose. *Location*: https://docs.mongodb.com/manual/aggregation/ *User-Agent*: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 *Referrer*: https://www.mongodb.com/contact *Screen Resolution*: 2400 x 1350
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:
{
_id: 1234,
name: "my name",
address:
}
after the upgrade / import:
{
_id: 1234,
name: "my name",
address:
}