[DRIVERS-2604] Queryable Encryption prose and spec tests can share the same encryptedFields JSON files Created: 12/Apr/23 Updated: 21/Aug/23 |
|
| Status: | Implementing |
| Project: | Drivers |
| Component/s: | Client Side Encryption |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Jeremy Mikola | Assignee: | Kevin Albertson |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Downstream Changes Summary: | resync range-... and fle2v2-... files to https://github.com/mongodb/specifications/commit/c4f3fabe9047e5e7a87877d642fa0d885a47351c There is no expected test coverage or behavior change. Consider closing the language ticket as "Won't Do" and resyncing test files as part of a future change. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Engineering Lead: | |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Start date: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
SummaryCSFLE prose test 22 uses range-encryptedFields-<type>.json files (added in There appear to be two notable differences:
It should be feasible to resolve these differences and have the prose and spec tests use the same set of JSON files. See this GitHub review comment for additional context. MotivationIs this issue urgent?No. Is this ticket required by a downstream team?No. Is this ticket only for tests?Yes. |
| Comments |
| Comment by Githook User [ 24/Apr/23 ] |
|
Author: {'name': 'Kevin Albertson', 'email': 'kevin.albertson@mongodb.com', 'username': 'kevinAlbs'}Message: DRIVERS-2604 deduplicate encrypted fields files (#1400)
If contention is not present, the server will provide a default value.
Server accepts either. Use numberLong for consistency.
|
| Comment by Kevin Albertson [ 12/Apr/23 ] |
|
In review here: https://github.com/mongodb/specifications/pull/1400 |