[DRIVERS-2655] Include Connection URI Options as Handshake Metadata Created: 15/Jun/23 Updated: 15/Jun/23 Resolved: 15/Jun/23 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Handshake |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | Alex Bevilacqua | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||
| Description |
|
As the Connection String Spec states "... Keys that aren't supported by a driver MUST be ignored. A WARN level logging message MUST be issued for unsupported keys. ... and "... Any invalid Values for a given key MUST be ignored and MUST log a WARN level message. ...", any invalid configuration options would only ever be surfaced client-side. By communicating the URI Option Keys and URI Option Values during the driver handshake, this information would be available in the mongos and mongod logs. This would support teams understand what options (both valid and invalid) are being configured, as well as how prevalent certain configurations are in the field. |
| Comments |
| Comment by Alex Bevilacqua [ 15/Jun/23 ] |
|
Thanks shane.harvey@mongodb.com |
| Comment by Shane Harvey [ 15/Jun/23 ] |
|
This may be a duplicate of DRIVERS-821. |