Details
-
Spec Change
-
Resolution: Unresolved
-
Minor - P4
-
None
-
None
-
None
-
Needed
Description
As part of work on unifying behavior around configuration for replica set discovery, we discussed that the drivers should be using server description of the server to which an operation would be sent to determine whether the operation would be supported, rather than topology type. For example, if a driver is connected to a replica set member in Single topology, retryable reads and writes, sessions and transactions should be supported because the underlying server supports them.
This ticket covers spec changes across existing specifications explicitly stating that the feature detection should be based on server description, not topology type.
According to my investigation the following specifications should be examined for possible changes/clarifications:
Enumerate-collections - listCollections on replica set members
Enumerate-indexes - listIndexes on replica set members
Enumerate-databases - listDatabases on replica set members
Driver-read-preference - command helpers and secondaries
Causal-consistency - test cases
Retryable-writes - supported server versions
Retryable-reads - supported server versions
Sessions - how to determine whether deployment supports sessions
Transactions - startTransaction - server support of transactions