For new metadata fields added in this project (I think just "score" and "scoreDetails"), we should fail the query if we try to reference the metadata field when it's not defined. For example, the pipeline {$project: {$meta: "score"}} should fail since "score" is not populated.
We should also think about how this interacts with "searchScore" and "searchScoreDetails".
It's unclear how challenging this will be to pull off, but we should at least investigate it.
- depends on
-
SERVER-99596 Refactor how metadata dependencies are validated
-
- Closed
-
- is depended on by
-
SERVER-99153 $rankFusion scoreDetails should error if not requested by top-level pipeline (but specified in inner)
-
- Open
-
- is related to
-
SERVER-100404 $meta field validation is inconsistent on sharded collections
-
- Open
-
-
SERVER-93521 Enforce that "searchScore" and "vectorSearchScore" cannot be used when undefined.
-
- Backlog
-
- related to
-
SERVER-99153 $rankFusion scoreDetails should error if not requested by top-level pipeline (but specified in inner)
-
- Open
-
-
SERVER-100945 Enable "score" for $facet subpipelines
-
- Backlog
-
-
SERVER-100946 Enable "score" for $facet subpipelines
-
- Backlog
-
-
SERVER-101004 Complete TODO listed in SERVER-99169
-
- Blocked
-
-
SERVER-100678 scoreDetails cannot be used when not defined
-
- In Progress
-