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

Let crypto code deal with optional min/max

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query Optimization

    Description

      Right now the FLE2RangeFindSpec mandates non-optional min/max for the encrypted index, when the crypto code can in fact handle optional values for these fields. This ticket should:
      1. Make the fields optional
      2. add the indexType to the find spec
      3. Update code to handle optional types and propagate optional from the encrypted field config.

      Attachments

        Activity

          People

            backlog-query-optimization Backlog - Query Optimization
            davis.haupt@mongodb.com Davis Haupt (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: