[FLE] Implement ability to track renamed/modified encrypted fields in an agg pipeline

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Aggregation Framework
    • None
    • Query 2019-03-11, Query 2019-03-25, Query 2019-04-08, Query 2019-04-22, Query 2019-05-06
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Nicholas Zolnierz
              Reporter:
              Nicholas Zolnierz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: