I wanna confirm if the meanings of these terms make sense:
WindowMaterializationLayout::Pane -- non-overlapping instance of a window i.e. instance of a tumbling windowWindowMaterializationLayout::FullWindow -- one complete query-width state per slide/evaluation point
Related questions:
WindowMaterializationLayout::HierarchicalRollup -- is this used? Didn't understand the meaning- window -- are we confusing the concept between how data is summarized into summaries vs what the query asks for?
- boundary -- similar to window, are we confusing this between the path where we summarize data into summaries, and the path where we use summaries for query results?
- Given, we already have the
WindowKind enum, I do not understand what the WindowMaterializationLayout enum is for.
- ASAPPlanner has
SummaryWindowFramework. Do we require a separate WindowKind enum?
I wanna confirm if the meanings of these terms make sense:
WindowMaterializationLayout::Pane-- non-overlapping instance of a window i.e. instance of a tumbling windowWindowMaterializationLayout::FullWindow-- one complete query-width state per slide/evaluation pointRelated questions:
WindowMaterializationLayout::HierarchicalRollup-- is this used? Didn't understand the meaningWindowKindenum, I do not understand what theWindowMaterializationLayoutenum is for.SummaryWindowFramework. Do we require a separateWindowKindenum?