-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-37589][SQL][TESTS] Improve the performance of PlanParserSuite
#34841
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 |
|
Test build #146023 has finished for PR 34841 at commit
|
|
ping @cloud-fan |
dongjoon-hyun
left a comment
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.
Could you give us some improvement numbers in the PR description, @beliefer ?
So we can reduce the time spent on executing PlanParserSuite by replace parsePlan.
PlanParserSuitePlanParserSuite
| comparePlans(parsePlan(sqlCommand), plan, checkAnalysis = false) | ||
| } | ||
|
|
||
| private def assertQueryEqual(query: String, plan: LogicalPlan): Unit = { |
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.
This makes it hard to write tests as people need to pick between assertEqual and assertQueryEqual.
How much we can speed up this test suite by doing so?
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.
About tens of milliseconds
|
Maybe it not worth. |
|
Thank you for closing, @beliefer . |
What changes were proposed in this pull request?
#34543 provides the parse method
parseQuery. So we can reduce the time spent on executingPlanParserSuiteby replaceparsePlan.Why are the changes needed?
Improve the performance of
PlanParserSuite.Does this PR introduce any user-facing change?
'No'.
Just update tests.
How was this patch tested?
Jenkins test.