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

Consider manually splitting by '.' and hashing field names for paths which can't be converted to FieldPath

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • Fully Compatible
    • QO 2023-06-26, QO 2023-07-10

      Some valid field names are considered invalid as a FieldPath (for example, fields like "foo.$bar" where a sub-component is prefixed with "$"). Currently, if serializeFieldPath errors due to supposedly "invalid" field names, we instead serialize that field name with a placeholder string.

      We should consider options to redact field names that are considered invalid to the FieldPath validation and remove any use of a placeholder string. The most obvious albeit non-optimal solution would be to manually split the string into its sub-components, then (as is done in serializeFieldPath) run the redaction policy over each component and reconstruct the redacted field.

            Assignee:
            naafiyan.ahmed@mongodb.com Naafiyan Ahmed
            Reporter:
            will.buerger@mongodb.com Will Buerger
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: