[MONGOCRYPT-121] Properly handle duplicate key conflicts Created: 11/May/19 Updated: 28/Oct/23 Resolved: 24/Aug/19 |
|
| Status: | Closed |
| Project: | Libmongocrypt |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.0-beta5 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kevin Albertson | Assignee: | Kevin Albertson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
Came out of Copied from the code review:
|
| Comments |
| Comment by Githook User [ 26/Aug/19 ] |
|
Author: {'username': 'kevinAlbs', 'email': 'kevin.albertson@mongodb.com', 'name': 'Kevin Albertson'}Message: |
| Comment by Githook User [ 24/Aug/19 ] |
|
Author: {'username': 'kevinAlbs', 'email': 'kevin.albertson@mongodb.com', 'name': 'Kevin Albertson'}Message:
|
| Comment by Kevin Albertson [ 03/Jun/19 ] |
|
Some additional ideas that came out of this review for In an event that we have two keys with intersecting key alt names but different key ids, the simplest approach may be to flush the cache. |