[SERVER-39403] [FLE] Implement ability to track renamed/modified encrypted fields in an agg pipeline Created: 06/Feb/19  Updated: 27/Oct/23  Resolved: 25/Apr/19

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

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

Issue Links:
Depends
depends on SERVER-39223 Implement extracting encrypted paths ... Closed
depends on SERVER-40312 [FLE] Add a method for walking a Pipe... Closed
is depended on by SERVER-39395 [FLE] Implement replacement of encryp... Closed
is depended on by SERVER-39397 [FLE] Implement method for building a... Closed
is depended on by SERVER-39399 [FLE] Implement ability to detect whe... Closed
Sprint: Query 2019-03-11, Query 2019-03-25, Query 2019-04-08, Query 2019-04-22, Query 2019-05-06
Participants:

 Description   

Walk a pipeline and figure out what base field is referred to by something like "$a". Start with a JSONSchema and track mutations of it as we go along the pipeline.

After this ticket we will have the ability to say at any given point in the pipeline whether a field should be encrypted. We should also be able to detect whether we need to fail if it is ambiguous.



 Comments   
Comment by Nicholas Zolnierz [ 25/Apr/19 ]

Closing this ticket as I've split up the remaining tasks by aggregation stage. 

Comment by Githook User [ 11/Apr/19 ]

Author:

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

Message: Revert "SERVER-39403 Implement DocumentSource visitor for sources in enterprise"

This reverts commit dfe08e0eb323a8058399abc5d2a45c7d6390c320.
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/85126c8d1419c21d1063d460527ddde201de3a47

Comment by Githook User [ 11/Apr/19 ]

Author:

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

Message: Revert "SERVER-39403 Implement visitor for DocumentSource as precursor work for"

This reverts commit 1b00abfda7592d701f632b9550f973c56cea818f.
Branch: master
https://github.com/mongodb/mongo/commit/3b41d489010fec3502bd18e1092bb3f325813456

Comment by Githook User [ 10/Apr/19 ]

Author:

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

Message: SERVER-39403 Implement DocumentSource visitor for sources in enterprise
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/dfe08e0eb323a8058399abc5d2a45c7d6390c320

Comment by Githook User [ 10/Apr/19 ]

Author:

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

Message: SERVER-39403 Implement visitor for DocumentSource as precursor work for
encryption in agg
Branch: master
https://github.com/mongodb/mongo/commit/1b00abfda7592d701f632b9550f973c56cea818f

Comment by Nicholas Zolnierz [ 22/Mar/19 ]

jacob.evans per in-person discussion, I've split out your pipeline tree into SERVER-40312 and left this ticket as the FLE-specific logic. Our thoughts for this ticket were a visitor pattern on DocumentSource which accepts a pointer to the source and a schema, returning a potentially modified schema to be passed to the next stage.

Comment by Githook User [ 13/Mar/19 ]

Author:

{'name': 'Jacob Evans', 'email': 'jacob.evans@10gen.com'}

Message: SERVER-39403 Enable accessing sub-pipeline from public const context
Branch: master
https://github.com/mongodb/mongo/commit/e3407fe85774f6b8b0a76eef1a3040321537b760

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