Skip to content

branch-2.1: [fix](nereids)alter sql block rule lost sql pattern info #53559 #54093

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.

Sign up for GitHub

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

Jump to bottom
Open
github-actions wants to merge 1 commit into
base: branch-2.1
Choose a base branch
from
Open

branch-2.1: [fix](nereids)alter sql block rule lost sql pattern info #53559 #54093

github-actions wants to merge 1 commit into from

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jul 30, 2025

Cherry-picked from #53559

@starocean999
[fix](nereids)alter sql block rule lost sql pattern info (#53559)
fbd7a11 
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
@github-actions github-actions bot requested a review from yiguolei as a code owner July 30, 2025 08:26
@hello-stephen
Copy link
Contributor

hello-stephen commented Jul 30, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring reopened this Jul 30, 2025
@hello-stephen
Copy link
Contributor

hello-stephen commented Jul 30, 2025

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei Awaiting requested review from yiguolei yiguolei is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@hello-stephen @dataroaring @starocean999