[SERVER-41485] [FLE] Mark literals for encryption that will be written as part of pipeline updates Created: 03/Jun/19 Updated: 05/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Jacob Evans | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Sprint: | Query 2019-06-17 | ||||||||
| Participants: | |||||||||
| Description |
|
Without this task, all literals will be assumed to be unencrypted if not sourced from an already encrypted field and failure will occur if we attempt to update an encrypted field with a literal. We can improve this situation by maintaining a set of literals headed to "Fowarded" output. Once we are done walking the pipeline, if headed to an encrypted field, we can mark each member of the set for encryption. We could also use the mechanism to mark literals that were part of previous stages in non-update pipelines for extra credit. |
| Comments |
| Comment by Githook User [ 18/Jun/19 ] |
|
Author: {'name': 'Jacob Evans', 'email': 'jacob.evans@10gen.com'}Message: SERVER-41485 Make tree type to support yet-to-be-determined encryption |
| Comment by Githook User [ 18/Jun/19 ] |
|
Author: {'name': 'Jacob Evans', 'email': 'jacob.evans@10gen.com'}Message: SERVER-41485 Make tree type to support yet-to-be-determined encryption |