[COMPASS-5586] Compass MongoDB compatibility Created: 15/Mar/22 Updated: 10/Jan/24 Resolved: 15/Mar/22 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Compass |
| Affects Version/s: | 1.30.1 |
| Fix Version/s: | No version |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Néstor Waldyd | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Documentation Changes: | Not Needed |
| Description |
| Comments |
| Comment by Massimiliano Marcon [ 15/Mar/22 ] |
|
MongoDB 3.2 was EOLed a long time ago (in Sep 2018). For Compass to be compatible with such an old version of MongoDB, we'd have to put in place workarounds for functionality that was not in the server or in the drivers that were compatible with 3.2 and this would result in a worse user experience. If you still need to work with MongoDB 3.2, I would recommend downloading an old version of Compass (all our releases are available at https://github.com/mongodb-js/compass/releases). Similarly, if you are looking for a version of the Node.js driver that works with 3.2, you can install an old version of the driver. From the screenshots you shared, I assume you are using CosmosDB. I think you might be able to configure it to be 3.6 compatible but even with that it will support a very limited subset of the MongoDB API so Compass might not work in the most optimal way. |
| Comment by Néstor Waldyd [ 15/Mar/22 ] |
|
|