[JAVA-3752] Client-side encryption not applied in a transaction on a sharded cluster Created: 02/Jun/20 Updated: 28/Oct/23 Resolved: 04/Jun/20 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Client Side Encryption, Transaction Management |
| Affects Version/s: | None |
| Fix Version/s: | 3.12.6, 4.0.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
The mongos pinning logic for sharded transactions does not interact properly with automatic client-side encryption, causing the encryption/decryption logic to not execute. |
| Comments |
| Comment by Githook User [ 04/Jun/20 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Apply client-side encryption in transactions on sharded clusters This fixes a bug in both sync and async drivers where client-side
|