Add IFR flag retry logic to route $vectorSearch-in-a-view and -in-a-subpipeline through legacy $vectorSearch

XMLWordPrintableJSON

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

      See design doc tab IFR Flag Kick-back-and-retry. This ticket should probably aim to finish steps 4 and 5, and make a (noPassthrough?) test to show that a cluster with a router and a shard having different values of the feature flag will still result in predictable $vectorSearch results based on the router's feature flag value. 

            Assignee:
            Finley Lau
            Reporter:
            Will Buerger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: