-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: None
-
None
-
Needed
-
Summary
Do not connect to mongocryptd if shared library is loaded
Motivation
Successfully loading shared library implicitly assumed that MongoClient must not be created for mongocryptd, now this statement is explicit.
How does this affect the end user?
If a driver spawns a MongoClient for mongocryptd when a shared library is in place, this client will be no-op if mongocryptd is available and will generate hidden SDAM exceptions in another case.
Is this issue urgent?
Nothing is on fire, but better to check this behavior to avoid confusions like why I see mongocryptd exceptions/calls when I use shared library
Is this ticket only for tests?
no
- related to
-
DRIVERS-2451 Test mongocryptd is not spawned when shared library is loaded
- Closed
- split to
-
CXX-2578 Do not connect to mongocryptd if shared library is loaded
- Backlog
-
PHPLIB-988 Do not connect to mongocryptd if shared library is loaded
- Blocked
-
CDRIVER-4480 Do not connect to mongocryptd if shared library is loaded
- Closed
-
CSHARP-4335 Do not connect to mongocryptd if shared library is loaded
- Closed
-
GODRIVER-2559 Do not connect to mongocryptd if shared library is loaded
- Closed
-
JAVA-4741 Do not connect to mongocryptd if shared library is loaded
- Closed
-
MOTOR-1034 Do not connect to mongocryptd if shared library is loaded
- Closed
-
NODE-4663 Do not connect to mongocryptd if shared library is loaded
- Closed
-
PYTHON-3446 Do not connect to mongocryptd if shared library is loaded
- Closed
-
RUBY-3133 Do not connect to mongocryptd if shared library is loaded
- Closed
-
RUST-1479 Do not connect to mongocryptd if shared library is loaded
- Closed