Meteor-feature-requests: mongodb 3.6 ? 1.6.1 ?

[crapthings]

https://docs.mongodb.com/manual/release-notes/3.6/#known-issues-in-3-6-0

[StorytellerCZ]

What is this about?
MongoDB 3.6 discussion is already happening:
https://github.com/meteor/meteor-feature-requests/issues/152
https://github.com/meteor/meteor-feature-requests/issues/158

[jamesgibson14]

A pretty simple request to add MongoDB 3.6 and the latest node driver to Meteor, after that we can continue to have discussions on how best take advantage and implement the new features like change notifications, expressive queries in Minimongo, etc.

[hwillson]

Taking change streams out of the picture for now, we can still move ahead with updating the Meteor Tool to use Mongo 3.6. Marking as pull-requests-encouraged if anyone is interested in helping out!

[hwillson]

Quick FYI - this work is being handled in https://github.com/meteor/meteor/pull/9632.

[klaussner]

MongoDB has been updated to version 3.6 in Meteor 1.7.

[rijk]

The error reported in https://github.com/meteor/meteor/issues/9753 is still happening when using the aggregate() function with Meteor 1.7.0.3.. Are you guys aware of this?

[klaussner]

@rijk Can you open a new issue for that (with a reproduction repo)? :slightly_smiling_face:

[rijk]

@klaussner while creating the reproduction repo, I found out that this is not strictly a bug, but a subtle change of API between Meteor 1.6/Mongo 3.4 and 1.7/3.6. Namely, the .aggregate() function used to directly return an array, but now it returns an AggregationCursor. I have to manually call toArray() after aggregate(). Not sure if this was an intended change, though.

[klaussner]

Yes, that's an intended change. The new version of the MongoDB driver used in Meteor 1.7 is a major update with a few breaking changes that you need to consider if you a using the "raw" driver functions. See also https://github.com/meteor/meteor/issues/9936#issuecomment-394514613.