[JAVA-4257] Default directConnection to false even if only one host is specified Created: 22/Jul/21  Updated: 27/Jul/23

Status: Backlog
Project: Java Driver
Component/s: Configuration
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Unknown
Reporter: Jeffrey Yemin Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DRIVERS-737 Unify behavior around configuration f... Closed
Documentation Changes: Needed

 Description   

See https://github.com/mongodb/specifications/blob/b07c26dc40d04ac20349f989db531c9845fdd755/source/server-discovery-and-monitoring/server-discovery-and-monitoring.rst#initial-topologytype

If the directConnection option is not specified, newly developed drivers MUST behave as if it was specified with the false value.

Since changing the starting topology can reasonably be considered a backwards-breaking change, existing drivers SHOULD stage implementation according to semantic versioning guidelines. Specifically, support for the directConnection URI option can be added in a minor release. In a subsequent major release, the default starting topology can be changed to Unknown. Drivers MUST document this in a prior minor release.

In 4.1.0 support for directConnection was added, but we didn't change the default behavior of the driver as required by the spec. We should do it in the next major release.



 Comments   
Comment by Jeffrey Yemin [ 27/Jul/23 ]

Removed the 5.0 fix version. We may never do this, but leaving it in the backlog for now, since it's still in the spec.

Generated at Thu Feb 08 09:01:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.