Hybrid search is not banned on sharded timeseries collections inside $unionWith and $lookup subpipelines

XMLWordPrintableJSON

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

      The issue is that a shard does not know information about the timeseries view of the remote shard that will be responsible for running it, but desugaring seems to be happening on the shard running the primary query. Thus we do not have all the information to know both a) is it a hybrid search query and b) is the subpipeline on a timeseries collection

            Assignee:
            Unassigned
            Reporter:
            Finley Lau
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: