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

POC WindowManager class and interface

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Query Optimization

    Description

      The idea with the WindowManager is to act as a middle-man between the aggregation stage (which receives documents and outputs documents) and the window functions (which accumulate values, potentially remove, and return a computed result).

      Some concepts that would be worth hashing out:

      • How will the stage logic interact with the WindowManager? Or vice versa?
        • Likewise, who is responsible for driving the pulling of the next document in the pipeline?
      • Can we assume that all docs in a partition will be buffered?
      • What sort of state is shared across the different WindowManagers and what is unique?
      • When the stage detects a new partition, what is the exact sequence of events to populate the remaining documents? This piece will likely require logic in both the stage and the window manager

      Attachments

        Activity

          People

            backlog-query-optimization Backlog - Query Optimization
            nicholas.zolnierz@mongodb.com Nicholas Zolnierz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: