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

Stress test dependency tracking for {$meta: "score"} for pipelines spanning across sharded network split

    • Type: Icon: Engineering Test Engineering Test
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration

      Follow-up work to SERVER-96792 - and related to SERVER-93521 - I remembered that there's some logic related to tracking usage of textScore metadata when we split the pipeline. I think we need to (a) make sure we didn't screw this up if you use $meta: "score" instead of $meta: "textScore" by adding some tests with references to "score" in some piece of the pipeline we know will execute after a split point and (b) see if this code might have hints about how we could implement SERVER-93521. It seems like the text search scenario would give a good example of how to do this. Relatedly, we should probably (c) add tests for the similar cases of split pipelines with $search and $vectorSearch also.

            Assignee:
            Unassigned Unassigned
            Reporter:
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: