Substrait: Add support for WindowFunction #5653
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes # 5390.
Rationale for this change
Added the ability to producer/consume Substrait plans with WindowFunction
What changes are included in this PR?
LogicalPlan::WindowcaseProjectRel, appendWindowFunctionexpressions before returning the parsedProjectRelProjectRel, add column reference expressions to represent ALL of the fields of the input relation's output. Then appendWindowFunctionexpressions.WindowFunctionWindowFrameUnitsare currently set to eitherRowsorRangedepending on whetherORDER BYis present in theWindowFunction. May need to revisit the cases when frame is explicitly defined.from_substrait_sorts()ORDER BYPARTITION BYWindowFunctionexpressions with column referenceAre these changes tested?
Yes. (cases explained above)
Are there any user-facing changes?
No