-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-36223][SQL][TEST] Cover 3 kinds of join in the TPCDSQueryTestSuite #33510
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
a603ffc to
46bbf1f
Compare
sql/core/src/test/scala/org/apache/spark/sql/TPCDSQueryTestSuite.scala
Outdated
Show resolved
Hide resolved
sql/core/src/test/scala/org/apache/spark/sql/TPCDSQueryTestSuite.scala
Outdated
Show resolved
Hide resolved
42bb832 to
763c492
Compare
sql/core/src/test/scala/org/apache/spark/sql/TPCDSQueryTestSuite.scala
Outdated
Show resolved
Hide resolved
sql/core/src/test/scala/org/apache/spark/sql/TPCDSQueryTestSuite.scala
Outdated
Show resolved
Hide resolved
sql/core/src/test/scala/org/apache/spark/sql/TPCDSQueryTestSuite.scala
Outdated
Show resolved
Hide resolved
sql/core/src/test/scala/org/apache/spark/sql/TPCDSQueryTestSuite.scala
Outdated
Show resolved
Hide resolved
|
ok to test |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #145066 has finished for PR 33510 at commit
|
sql/core/src/test/scala/org/apache/spark/sql/TPCDSQueryTestSuite.scala
Outdated
Show resolved
Hide resolved
sql/core/src/test/scala/org/apache/spark/sql/TPCDSQueryTestSuite.scala
Outdated
Show resolved
Hide resolved
|
Kubernetes integration test starting |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Kubernetes integration test status failure |
|
Kubernetes integration test status failure |
|
Test build #145167 has finished for PR 33510 at commit
|
|
Test build #145170 has finished for PR 33510 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Kubernetes integration test starting |
|
thanks, merging to master! |
|
Kubernetes integration test status failure |
|
Thank you @cloud-fan @linhongliu-db and @HyukjinKwon for review. |
|
Test build #145222 has finished for PR 33510 at commit
|
|
Test build #145223 has finished for PR 33510 at commit
|
| assertResult(expectedSchema, s"Schema did not match\n$queryString") { schema } | ||
| assertResult(expectedOutput, s"Result did not match\n$queryString") { outputString } | ||
| } | ||
| val joinConfSet: Set[Map[String, String]] = |
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.
Hm, why is this set? Then joinConfSet.head won't be deterministic below, and there would be no point of needSort.
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.
Let me fix it together at #34698
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.
Yes, seq may be better.
### What changes were proposed in this pull request? This is kind of a followup for #33510 and #34641. This PR proposes to split TPC-DS build in GitHub Actions. ### Why are the changes needed? Running these queries easily causes out-of-memory in GitHub Actions machines, and make the build flaky. We should deflake it. ### Does this PR introduce _any_ user-facing change? No, dev-only. ### How was this patch tested? GitHub Actions in this PR should test it out. Closes #34698 from HyukjinKwon/split-tpcds. Authored-by: Hyukjin Kwon <[email protected]> Signed-off-by: Hyukjin Kwon <[email protected]>
What changes were proposed in this pull request?
In current github actions we run TPCDSQueryTestSuite for tpcds benchmark. But it's only tested under default configurations. Since we have added the
spark.sql.join.forceApplyShuffledHashJoinconfig. Now we can test all 3 join strategies in TPCDS to improve the coverage.Why are the changes needed?
Improve the coverage of join strategies in the TPCDS.
Does this PR introduce any user-facing change?
No, only for testing.
How was this patch tested?
No need.