-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-25862][SQL] Remove rangeBetween APIs introduced in SPARK-21608 #22870
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
|
Test build #98173 has finished for PR 22870 at commit
|
| (lower, upper) match { | ||
| case (l: Expression, u: Expression) if !isValidFrameBoundary(l, u) => | ||
| TypeCheckFailure(s"Window frame upper bound '$upper' does not followes the lower bound " + | ||
| TypeCheckFailure(s"Window frame upper bound '$upper' does not follow the lower bound " + |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to generate the result file for org.apache.spark.sql.SQLQueryTestSuite
Fix tests at PR 22870
|
Test build #98180 has finished for PR 22870 at commit
|
|
retest this please |
|
Test build #98184 has finished for PR 22870 at commit
|
|
retest this please. |
|
Test build #98191 has finished for PR 22870 at commit
|
|
LGTM Thanks! Merged to master. |
## What changes were proposed in this pull request? This patch removes the rangeBetween functions introduced in SPARK-21608. As explained in SPARK-25841, these functions are confusing and don't quite work. We will redesign them and introduce better ones in SPARK-25843. ## How was this patch tested? Removed relevant test cases as well. These test cases will need to be added back in SPARK-25843. Closes apache#22870 from rxin/SPARK-25862. Lead-authored-by: Reynold Xin <rxin@databricks.com> Co-authored-by: hyukjinkwon <gurwls223@apache.org> Signed-off-by: gatorsmile <gatorsmile@gmail.com>
What changes were proposed in this pull request?
This patch removes the rangeBetween functions introduced in SPARK-21608. As explained in SPARK-25841, these functions are confusing and don't quite work. We will redesign them and introduce better ones in SPARK-25843.
How was this patch tested?
Removed relevant test cases as well. These test cases will need to be added back in SPARK-25843.