[GODRIVER-2648] Mongo FLE keyvault collection has hardcoded majority read and write concern Created: 09/Nov/22 Updated: 15/Nov/22 |
|
| Status: | Backlog |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | Elena Flat | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Hello, currently the key vault has hardcoded majority read and write concern: https://github.com/mongodb/mongo-go-driver/blob/master/mongo/client.go#L40-L46
This does not let us run our applications with any other concern, since our applications utilize FLE. Even if the rest of the application uses read local and w=1, the key vault reads will hang indefinitely if a majority read is not currently available. What is the rationale behind this? Would you be open to allowing a config entry point that would allow to change the read and write concern on the key vault to something else?
Thank you,
Elena Flat |
| Comments |
| Comment by Kevin Albertson [ 09/Nov/22 ] |
|
Hello eflat@league.com Using majority read and write concern is a requirement of the driver specification https://github.com/mongodb/specifications/blob/d268119c9d4354f60e59d2e798c3cb3ee5323a29/source/client-side-encryption/client-side-encryption.rst#key-vault-collection:
DRIVERS-1960 tracks the request to make it configurable. Please watch that ticket for updates.
|