[SERVER-53901] FLE EncryptSchemaKeyId parser should provide better error message Created: 20/Jan/21 Updated: 29/Oct/23 Resolved: 10/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Anna Henningsen | Assignee: | Alya Berciu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | quick-tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
The error message in src/mongo/db/matcher/schema/encrypt_schema_types.cpp#L44-L46 is very vague. In particular, this is confusing because (at least with the Node.js libmongocrypt bindings, but likely also the others) the error shows up when actually trying to insert documents using this schema, rather than when the schema is first specified. This makes it seem like something is wrong with the inserted document, rather than the schema itself. I will open a pull request with a suggestion. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 10/Sep/21 ] |
|
Author: {'name': 'Anna Henningsen', 'email': 'anna.henningsen@mongodb.com', 'username': 'addaleax'}Message: |