[AURON #2176] Implement native support for lead window function#2188
Draft
weimingdiit wants to merge 2 commits intoapache:masterfrom
Draft
[AURON #2176] Implement native support for lead window function#2188weimingdiit wants to merge 2 commits intoapache:masterfrom
weimingdiit wants to merge 2 commits intoapache:masterfrom
Conversation
25 tasks
efe00fc to
5fd852f
Compare
Signed-off-by: weimingdiit <weimingdiit@gmail.com>
5fd852f to
7f1fef3
Compare
Signed-off-by: weimingdiit <weimingdiit@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #2176
Rationale for this change
Auron’s native window support previously covered rank-like functions and a subset of aggregate window functions, but did not support offset-based window functions such as
lead(...).This PR extends native window coverage with a conservative first step:
lead(...)input,offset, anddefaultWhat changes are included in this PR?
This PR:
Leadhandling inNativeWindowBaseLEADLEADinto the native window planLeadProcessorindatafusion-ext-plansleadusing Spark-compatible offset/default/null behaviorleadso that lookahead works correctly across input batchesleadlead(...)executionlead(... ) IGNORE NULLSThe native implementation supports Spark semantics for:
lead(input)1nulllead(input, offset, default)inputat theoffsetth row after the current row in the same window partitioninputthere isnull, returnsnulldefaultSupported scope in this PR:
RESPECT NULLSbehaviorNot supported natively in this PR:
IGNORE NULLSUnsupported
IGNORE NULLSqueries continue to fall back to Spark to preserve correctness.Are there any user-facing changes?
Yes.
Queries using
lead(...)can now remain on Auron’s native window execution path when they use supported semantics.Queries using unsupported
lead(... ) IGNORE NULLSbehavior will continue to fall back to Spark.How was this patch tested?
CI.