-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[opt](nereids) Add planWithUnknownColumnStats to QueryState to prevent queries from analysis tasks from polluting the column stats cache. #57850
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
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-H: Total hot run time: 34365 ms |
TPC-DS: Total hot run time: 187715 ms |
ClickBench: Total hot run time: 27.52 s |
|
run cloud_p0 |
|
run nonConcurrent |
FE Regression Coverage ReportIncrement line coverage |
|
run cloud_p0 |
FE Regression Coverage ReportIncrement line coverage |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
|
run buildall |
TPC-H: Total hot run time: 34385 ms |
TPC-DS: Total hot run time: 188224 ms |
ClickBench: Total hot run time: 27.31 s |
FE Regression Coverage ReportIncrement line coverage |
1 similar comment
FE Regression Coverage ReportIncrement line coverage |
…t queries from analysis tasks from polluting the column stats cache. (#57850) ### What problem does this PR solve? Add planWithUnknownColumnStats to QueryState to prevent queries from analysis tasks from polluting the column stats cache.
…t queries from analysis tasks from polluting the column stats cache. (#57850) ### What problem does this PR solve? Add planWithUnknownColumnStats to QueryState to prevent queries from analysis tasks from polluting the column stats cache.
### What problem does this PR solve? Related PR: #36760 #57850 Problem Summary: Fix stats unknown when calc sync mv plan statistics For SQLs that are related to statistics, we should not collect or compute statistics. Previously this was determined by the `isInternal` flag, but `isInternal` is too broad: it covers not only statistics-related SQL but also SQL used to generate materialized view plans. Materialized view plan generation requires statistics, so we introduce a new flag `isPlanWithUnKnownColumnStats` to indicate connections that are used for statistics-only operations (treat column statistics as unknown).
### What problem does this PR solve? Related PR: #36760 #57850 Problem Summary: Fix stats unknown when calc sync mv plan statistics For SQLs that are related to statistics, we should not collect or compute statistics. Previously this was determined by the `isInternal` flag, but `isInternal` is too broad: it covers not only statistics-related SQL but also SQL used to generate materialized view plans. Materialized view plan generation requires statistics, so we introduce a new flag `isPlanWithUnKnownColumnStats` to indicate connections that are used for statistics-only operations (treat column statistics as unknown).
### What problem does this PR solve? Related PR: #36760 #57850 Problem Summary: Fix stats unknown when calc sync mv plan statistics For SQLs that are related to statistics, we should not collect or compute statistics. Previously this was determined by the `isInternal` flag, but `isInternal` is too broad: it covers not only statistics-related SQL but also SQL used to generate materialized view plans. Materialized view plan generation requires statistics, so we introduce a new flag `isPlanWithUnKnownColumnStats` to indicate connections that are used for statistics-only operations (treat column statistics as unknown).
…t queries from analysis tasks from polluting the column stats cache. (apache#57850) ### What problem does this PR solve? Add planWithUnknownColumnStats to QueryState to prevent queries from analysis tasks from polluting the column stats cache.
…#58426) ### What problem does this PR solve? Related PR: apache#36760 apache#57850 Problem Summary: Fix stats unknown when calc sync mv plan statistics For SQLs that are related to statistics, we should not collect or compute statistics. Previously this was determined by the `isInternal` flag, but `isInternal` is too broad: it covers not only statistics-related SQL but also SQL used to generate materialized view plans. Materialized view plan generation requires statistics, so we introduce a new flag `isPlanWithUnKnownColumnStats` to indicate connections that are used for statistics-only operations (treat column statistics as unknown).
…t queries from analysis tasks from polluting the column stats cache. (apache#57850) ### What problem does this PR solve? Add planWithUnknownColumnStats to QueryState to prevent queries from analysis tasks from polluting the column stats cache.
…t queries from analysis tasks from polluting the column stats cache. (apache#57850) ### What problem does this PR solve? Add planWithUnknownColumnStats to QueryState to prevent queries from analysis tasks from polluting the column stats cache.
### What problem does this PR solve? Related PR: #36760 #57850 Problem Summary: Fix stats unknown when calc sync mv plan statistics For SQLs that are related to statistics, we should not collect or compute statistics. Previously this was determined by the `isInternal` flag, but `isInternal` is too broad: it covers not only statistics-related SQL but also SQL used to generate materialized view plans. Materialized view plan generation requires statistics, so we introduce a new flag `isPlanWithUnKnownColumnStats` to indicate connections that are used for statistics-only operations (treat column statistics as unknown).
…#58426) ### What problem does this PR solve? Related PR: apache#36760 apache#57850 Problem Summary: Fix stats unknown when calc sync mv plan statistics For SQLs that are related to statistics, we should not collect or compute statistics. Previously this was determined by the `isInternal` flag, but `isInternal` is too broad: it covers not only statistics-related SQL but also SQL used to generate materialized view plans. Materialized view plan generation requires statistics, so we introduce a new flag `isPlanWithUnKnownColumnStats` to indicate connections that are used for statistics-only operations (treat column statistics as unknown).
What problem does this PR solve?
Add planWithUnknownColumnStats to QueryState to prevent queries from analysis tasks from polluting the column stats cache.
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)