Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-41485

[FLE] Mark literals for encryption that will be written as part of pipeline updates

    XMLWordPrintableJSON

Details

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Querying
    • None
    • Query Optimization
    • Query 2019-06-17

    Description

      Without this task, all literals will be assumed to be unencrypted if not sourced from an already encrypted field and failure will occur if we attempt to update an encrypted field with a literal. We can improve this situation by maintaining a set of literals headed to "Fowarded" output. Once we are done walking the pipeline, if headed to an encrypted field, we can mark each member of the set for encryption.

      We could also use the mechanism to mark literals that were part of previous stages in non-update pipelines for extra credit.

      Attachments

        Activity

          People

            backlog-query-optimization Backlog - Query Optimization
            jacob.evans@mongodb.com Jacob Evans
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: