[DRIVERS-770] Add runtime warning to drivers when connecting to a future version that may be incompatible Created: 30/Nov/19  Updated: 12/Jun/20  Resolved: 28/May/20

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Luke Prochazka Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related

 Description   

The impetus for this driver feature request is to proactively report any incompatible matches of driver/mongodb pairs (https://docs.mongodb.com/ecosystem/drivers/driver-compatibility-reference/).

For example, if Java driver v3.11 had baked in a mongod/mongos compat version 4.2 at the time of writing. Then the driver would log a warning when connecting to a future v4.4+, thereby flagging the potential incompatibility and encouraging the user to upgrade.

Optionally, you could also add a warning for a min compat version for the language/runtime.



 Comments   
Comment by Bernie Hackett [ 29/May/20 ]

The server versioned API makes this request unnecessary. The point of that feature is to allow users of MongoDB to develop an application against a specific version of MongoDB and its related driver release and be able to upgrade the server for the foreseeable future without having to change the application or driver version at all. Warning users that the driver might be incompatible "some day" defeats the purpose of the versioned API. That's why we've decided to close this ticket won't fix.

Comment by Alexander Golin (Inactive) [ 28/May/20 ]

Closing as this conflicts with the goals of the versioned API, which is trying to make it easy for old applications running with old driver version to connect to new server versions.

Generated at Thu Feb 08 08:22:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.