[SERVER-40243] Change EncryptionPlaceholder.algorithm to be integer based enum Created: 20/Mar/19 Updated: 29/Oct/23 Resolved: 04/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mark Benvenuto | Assignee: | Ted Tuckman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2019-04-08 |
| Participants: |
| Description |
|
The EncryptionPlaceholder should use a uint8 enum for algorithm instead of a string based enum. See update the BSON Binary subtype 6 spec. This will help keep the marking compat. |
| Comments |
| Comment by Githook User [ 04/Apr/19 ] |
|
Author: {'email': 'ted.tuckman@mongodb.com', 'name': 'Ted Tuckman', 'username': 'TedTuckman'}Message: |
| Comment by Githook User [ 04/Apr/19 ] |
|
Author: {'email': 'ted.tuckman@mongodb.com', 'name': 'Ted Tuckman', 'username': 'TedTuckman'}Message: |
| Comment by David Storch [ 25/Mar/19 ] |
|
nicholas.zolnierz, that sounds like a good idea. I slotted it into the 4/22 sprint as you suggest. |
| Comment by Nicholas Zolnierz [ 21/Mar/19 ] |
|
david.storch@mongodb.com I think we should bring this into the next sprint as it has driver implications. Any objection? |