Add MongoDB 5 compatibility

[mtrezza]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

PR to upgrade to mongodb node driver 4.x currently doesn't pass, needs some refactoring.
See #7586.

❗️ This is a critical upgrade for MongoDB 5 compatibility. All M0/M2/M5 Atlas clusters will automatically be upgraded to MongoDB 5.0 in early February 2022. That means after that, Parse Server will be incompatible with these and all free MongoDB Atlas plans.

A separate question is whether we want / can easily port this back to the 4.x branch. If not, then users of free or small (non-dedicated) MongoDB Atlas plans will be forced to upgrade to Parse Server 5.0. With that comes the necessity to adapt the deployment for the breaking changes in Parse Server 5.0.

Feature / Enhancement Description

Upgrade to the latest mongodb node driver.

Example Use Case

n/a

Alternatives / Workarounds

n/a

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[mtrezza]

@parse-community/server Anyone wants to take on this critical upgrade?
Given its time-criticality we'll also merge this into beta.

[Moumouls]

Hi @mtrezza

All M0/M2/M5 Atlas clusters will automatically be upgraded to MongoDB 5.0 in early February 2022. That means after that, Parse Server will be incompatible with these and all free MongoDB Atlas plans.

Do you have the Mongo DB announcement link, just to track the direct source of the issue ?

A separate question is whether we want / can easily port this back to the 4.x branch. If not, then users of free or small (non-dedicated) MongoDB Atlas plans will be forced to upgrade to Parse Server 5.0. With that comes the necessity to adapt the deployment for the breaking changes in Parse Server 5.0.

Here Mongo Node JS driver v4 migration guide: https://github.com/mongodb/node-mongodb-native/blob/4.0/docs/CHANGES_4.0.0.md

From my point of view and knowledge of parse-server, here the list of BK changes that can affect Parse:

• https://github.com/mongodb/node-mongodb-native/blob/4.0/docs/CHANGES_4.0.0.md#db-no-longer-emits-events (fixed in refactor: minor changes to remove mongo deprecation warnings #7626, but here in back port use case we will need to also backport my PR about db warnings)
• Grid FS: https://github.com/mongodb/node-mongodb-native/blob/4.0/docs/CHANGES_4.0.0.md#gridstore-removed
• replace returnOriginal with returnDocument option (already fixed by refactor: minor changes to remove mongo deprecation warnings #7626)
• update find and modify interfaces for 4.0
• remove top-level write concern options

As we saw in https://github.com/parse-community/parse-server/pull/7626/files, since Parse Mongo driver is globally well written, i think it's feasible to backport the mongo v5 PR to parse-server 4 without too many effort.

Here i'm also sorry i can't tell if i could work on this asap.

[mtrezza]

Do you have the Mongo DB announcement link, just to track the direct source of the issue ?

It's standard MongoDB Atlas procedure for free and shared clusters. These are always kept on the latest version and users have no control over the MongoDB version. We are actually late on upgrading because the 4.x driver has been released back in July 2021 already.

It's interesting though that we are currently running CI tests with MongoDB 5.0.3 but according to the compatibility table, MongoDB 5 requires the 4.x driver. Maybe this will be an Atlas specific restriction, or Parse Server is currently just not using or not testing features that are incompatible.

@dariakp do you have any insight to what extend the 3.x driver works with MongoDB 5 or should we open a ticket?

[dariakp]

@mtrezza I'm not sure I understand the question. The same features that work in the 3.x driver against pre-5.0 MongoDB servers should work against 5.0 MongoDB servers. However, the 3.x driver will not necessarily support the new features available in MongoDB 5.0. To get the new features, the 4.x driver should be used.