Mark constants for encryption in $lookup subpipelines

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      For an aggregation like

      coll.aggregate({$lookup: {from: "coll", as: "docs", pipeline: [{$match: {encryptedField: "1"}}])}}

      We do not mark the constant "1" for encryption in query analysis. But, we allow self-lookups with encrypted collections, so this kind of query should be supported.

      Once this is supported in query analysis, the server-side rewrites should be updated to support rewrites of subpipelines.

            Assignee:
            [DO NOT USE] Backlog - Query Optimization
            Reporter:
            Hana Pearlman
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: