-
Notifications
You must be signed in to change notification settings - Fork 236
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
add error section in report and the rest queries #9150
Conversation
Signed-off-by: Allen Xu <[email protected]>
Signed-off-by: Allen Xu <[email protected]>
@@ -0,0 +1,24 @@ | |||
package com.nvidia.spark.rapids.tests.scaletest |
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.
Missing license header
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.
Added.
@@ -0,0 +1,13 @@ | |||
package com.nvidia.spark.rapids.tests.scaletest |
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.
Missing license header
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.
Added.
Signed-off-by: Allen Xu <[email protected]>
Signed-off-by: Allen Xu <[email protected]>
Signed-off-by: Allen Xu <[email protected]>
build |
1 similar comment
build |
Hi @revans2 I've added all queries into the test suite, please help take a look when you have time. I've also put a query content list |
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.
In general it looks good, but I want to spend some time to test it myself. Just to be sure that the scale_factor/etc look correct and that the queries tax the plugin in ways we expect it to.
@@ -61,14 +243,14 @@ class QuerySpecs(config: Config, spark: SparkSession) { | |||
} | |||
} | |||
|
|||
def getCandidateQueries(): Map[String, TestQuery] = { | |||
def getCandidateQueries(): mutable.LinkedHashMap[String, TestQuery] = { |
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.
why are the maps mutable? Do we plan on changing them after they are constructed?
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.
I was looking for Map that can reserve insertion order and found LinkedHashMap first. I just found ListMap can also do this, updated.
config.iterations, | ||
config.timeout, | ||
"No obvious build side inner equi-join. (Shuffle partitions should be set to 10)", | ||
shufflePartitions = 10), |
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.
Why 10 shuffle partitions? The original proposal was ceil(scale_factor/50)
. Not that this is wrong, just curious.
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.
Oh I was refering to the queries in #8816. Now updated to what is set in test plan doc.
Signed-off-by: Allen Xu <[email protected]>
build |
1 similar comment
build |
I can build pipelines to test this, any test preference? According to the test plan doc, I should start to generate |
@wjxiz1992 lets check this in and then we can work on figuring out if we need to tweak things. We need to setup a pipeline anyways, so lets get started with that as a separate piece. |
Close #8816 and #9118
Close #9165 and #9166
This PR adds in
Not only the exceptions that a failed query throws, but also the exceptions that a Spark task failed at first but succeeded in retry. ([FEA] add error section in test report json file #9118)
--dry
: will only print the generated queries and its physical plan(.exlpain()
)This PR is still in testing with different scales, but it contains lots of queries, and it requires a lot of review for all of them since they are parsed according to my personal understanding. Put it up for early feedbacks.
put one generated queries for reviewers to help easy check the query correctness or if the queries are expected:
queries.txt