Consider parameterizing the $lookup inner pipeline at the optimization phase, not execution phase

XMLWordPrintableJSON

    • Query Optimization
    • 4
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The more fundamental issue that caused BF-28050 is that we repeatedly parse and optimize the $lookup inner pipeline for each input document, not parameterizing the inner pipeline.

      The classic $lookup would be used in foreseeable future given that the Nebari $lookup (hash lookup) does not support $lookup with inner pipeline and even though the Nebari $lookup supports $lookup with inner pipeline, it may take a while until we can fully switch to Nebari.

      Hope we could address this issue sooner or later.

              Assignee:
              [DO NOT USE] Backlog - Query Optimization
              Reporter:
              Yoon Soo Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: