[SERVER-39395] [FLE] Implement replacement of encrypted fields in a $match aggregation stage Created: 06/Feb/19  Updated: 29/Oct/23  Resolved: 13/May/19

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: 4.1.12

Type: Task Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Nicholas Zolnierz
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-39233 [FLE] Implement method for replacing ... Closed
depends on SERVER-39403 [FLE] Implement ability to track rena... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2019-05-06, Query 2019-05-20
Participants:

 Description   

This ticket should not handle renamed/modified fields before the $match stage. This may end up changing depending on SERVER-39403. The API for encrypting a match stage may need to take additional arguments depending on field renaming.



 Comments   
Comment by Githook User [ 13/May/19 ]

Author:

{'name': 'Nick Zolnierz', 'username': 'nzolnierzmdb', 'email': 'nicholas.zolnierz@mongodb.com'}

Message: SERVER-39395 Expose the ability the modify the expression of a $match stage
Branch: master
https://github.com/mongodb/mongo/commit/59f1f9e847ffbbdc48483d945611a93eae972114

Comment by Githook User [ 13/May/19 ]

Author:

{'name': 'Nick Zolnierz', 'username': 'nzolnierzmdb', 'email': 'nicholas.zolnierz@mongodb.com'}

Message: SERVER-39395 Translation for $match stage
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/4f977b9554b382260f580ade1b34402f5926841f

Generated at Thu Feb 08 04:51:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.