Literal and field name redaction for aggregation expressions
(SERVER-73325)
|
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Sub-task | Priority: | Major - P3 |
| Reporter: | Joshua Lapacik (Inactive) | Assignee: | Ted Tuckman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | QO 2023-02-06, QO 2023-02-20, QO 2023-03-06, QO 2023-03-20, QO 2023-04-03 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
As part of generating the telemetry key for an aggregation pipeline, we need to extend the serialization logic for all the aggregation expression types to support literal value redaction as well as field name redaction. For most aggregation operators, we'll want to replace literal values with a generic placeholder. This will require updating the serialization method of ExpressionConstant. We will also need to hash all user supplied field names, paths, and variables. This will require updating the serialization method of ExpressionFieldPath. Note that we will want to preserve MQL system variable references. |
| Comments |
| Comment by Githook User [ 16/Feb/23 ] |
|
Author: {'name': 'madelinezec', 'email': 'mez2113@columbia.edu', 'username': 'madelinezec'}Message: |
| Comment by Githook User [ 14/Feb/23 ] |
|
Author: {'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}Message: |