-
Notifications
You must be signed in to change notification settings - Fork 209
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
feat: dist sql analyze #1260
feat: dist sql analyze #1260
Conversation
fe189f3
to
9fafaca
Compare
Above is the result I get in local test, do you notice the empty metric sub plans still exist? You can't just finish the feature in some hack ways, which will make codes not maintainable, and should think about how to impl it following the datafusion metrics framework.
|
7f5847e
to
cd5b6b5
Compare
@baojinri Could you provide an example of the analysis result? |
Example result:
|
cd5b6b5
to
8051eec
Compare
726686d
to
99954b9
Compare
Add an integration test case for it. |
c838b10
to
fd6580c
Compare
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.
LGTM
## Rationale In #1260, we implemented distributed analyze, but for query that are not analyze, metrics will be returned, which will lead to a decrease in query performance. Therefore, we will fix it in this PR, and metrics will not be returned for normal queries. ## Detailed Changes - Add is_analyze field to determine whether it is analyze ## Test Plan Existing tests --------- Co-authored-by: jiacai2050 <dev@liujiacai.net>
Rationale
Currently, the analyze sql can not obtain detail metrics of partitioned table,
Detailed Changes
Test Plan