[SERVER-85011] POC WindowManager class and interface Created: 16/Dec/20  Updated: 13/Jan/24  Resolved: 14/Jan/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Backlog - Query Optimization
Resolution: Fixed Votes: 0
Labels: wf-m1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Optimization
Participants:

 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


 Comments   
Comment by Nicholas Zolnierz [ 14/Jan/21 ]

Closing this as there's now a server ticket tracking the work.

Generated at Thu Feb 08 06:56:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.