-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-33278][SQL][FOLLOWUP] Improve OptimizeWindowFunctions to avoid transfer first to nth_value. #30419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #131318 has finished for PR 30419 at commit
|
|
Test build #131321 has finished for PR 30419 at commit
|
|
retest this please |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #131335 has finished for PR 30419 at commit
|
|
cc @cloud-fan |
|
thanks, merging to master! |
What changes were proposed in this pull request?
#30178 provided
OptimizeWindowFunctionsused to transferfirsttonth_value.If the window frame is
UNBOUNDED PRECEDING AND CURRENT ROWorUNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING,nth_valuehas better performance thanfirst.But the
OptimizeWindowFunctionsneed to exclude other window frame.Why are the changes needed?
Improve
OptimizeWindowFunctionsto avoid transferfirsttonth_valueif the specified window frame isn'tUNBOUNDED PRECEDING AND CURRENT ROWorUNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING.Does this PR introduce any user-facing change?
'No'.
How was this patch tested?
Jenkins test.