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

Allow ExpressionMeta to parse find() $meta options

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Querying
    • Labels:
      None
    • Fully Compatible
    • Query 2019-08-26

      Add support for "recordId" "indexKey" and "sortKey" in ExpressionMeta.

      Like other meta types, the expression should returning "missing" if the associated metadata cannot be found on the Document.

      This ticket will also involve modifying Document and DocumentMetadataFields. The main purpose of this work is to make ExpressionMeta supercede find() $meta.

      Note that the work of figuring out how to pass metadata between the PlanStage and DocumentSource layer is tracked by SERVER-42560. This ticket is just about making $meta able to parse the new metadata options and retrieve them from a Document. Until we support expressions in find() projection, the change will not actually have any "visible" effects.

            Assignee:
            ian.boros@mongodb.com Ian Boros
            Reporter:
            ian.boros@mongodb.com Ian Boros
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: