-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](nereids)alter sql block rule lost sql pattern info #53559
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: 34239 ms |
TPC-DS: Total hot run time: 191472 ms |
ClickBench: Total hot run time: 32.66 s |
FE UT Coverage ReportIncrement line coverage |
|
run buildall |
TPC-H: Total hot run time: 34184 ms |
TPC-DS: Total hot run time: 191420 ms |
ClickBench: Total hot run time: 33.49 s |
FE UT Coverage ReportIncrement line coverage |
a13df4c to
09b0ce4
Compare
|
run buildall |
TPC-H: Total hot run time: 33865 ms |
TPC-DS: Total hot run time: 186723 ms |
ClickBench: Total hot run time: 32.4 s |
FE UT Coverage ReportIncrement line coverage |
| CREATE SQL_BLOCK_RULE rule_drop | ||
| PROPERTIES( | ||
| "sql"="select \\* from order_analysis", |
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.
not get the purpose of this case
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.
without the change, sqlPattern will be 'NULL', so 'select NULL' would hit this sql block rule
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
|
run check_coverage |
CREATE SQL_BLOCK_RULE rule_drop
PROPERTIES(
"sql"="select \\* from order_analysis",
"global"="true",
"enable"="true");
ALTER SQL_BLOCK_RULE rule_drop PROPERTIES("global"="true");
when ALTER SQL_BLOCK_RULE, we use new properties in the command and keep
other properties unchanged, but we need call setSqlPattern to fill the
new sql pattern or it will be 'NULL' which is a wrong pattern
CREATE SQL_BLOCK_RULE rule_drop
PROPERTIES(
"sql"="select \\* from order_analysis",
"global"="true",
"enable"="true");
ALTER SQL_BLOCK_RULE rule_drop PROPERTIES("global"="true");
when ALTER SQL_BLOCK_RULE, we use new properties in the command and keep
other properties unchanged, but we need call setSqlPattern to fill the
new sql pattern or it will be 'NULL' which is a wrong pattern
CREATE SQL_BLOCK_RULE rule_drop
PROPERTIES(
"sql"="select \\* from order_analysis",
"global"="true",
"enable"="true");
ALTER SQL_BLOCK_RULE rule_drop PROPERTIES("global"="true");
when ALTER SQL_BLOCK_RULE, we use new properties in the command and keep
other properties unchanged, but we need call setSqlPattern to fill the
new sql pattern or it will be 'NULL' which is a wrong pattern
## Proposed changes pick from apache#53559 <!--Describe your changes.-->
when ALTER SQL_BLOCK_RULE, we use new properties in the command and keep other properties unchanged, but we need call setSqlPattern to fill the new sql pattern or it will be 'NULL' which is a wrong pattern
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)