Skip to content

[feature](fe) Support dropping row policies by roles in batch#63329

Open
heguanhui wants to merge 1 commit into
apache:masterfrom
heguanhui:feature/drop-row-policy-by-roles
Open

[feature](fe) Support dropping row policies by roles in batch#63329
heguanhui wants to merge 1 commit into
apache:masterfrom
heguanhui:feature/drop-row-policy-by-roles

Conversation

@heguanhui
Copy link
Copy Markdown
Contributor

What problem does this PR solve?

Issue Number: close #xxx

Problem Summary: Currently, dropping row policies for multiple roles requires executing DROP ROW POLICY statement for each policy individually, which is cumbersome when a role has many policies. This PR adds a new syntax DROP ROW POLICY FOR ROLE role1, role2, ... to drop all row policies bound to the specified roles in one statement.

Release note

Support new syntax: DROP ROW POLICY FOR ROLE role1, role2, ... to drop all row policies bound to specified roles in batch.

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test
    • No need to test
  • Behavior changed:

    • No.
    • Yes. New SQL syntax DROP ROW POLICY FOR ROLE supported
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

### What problem does this PR solve?

Issue Number: close #xxx

Problem Summary: Currently, dropping row policies for multiple roles requires executing DROP ROW POLICY statement for each policy individually, which is cumbersome when a role has many policies. This PR adds a new syntax DROP ROW POLICY FOR ROLE role1, role2, ... to drop all row policies bound to the specified roles in one statement.

### Release note

Support new syntax: DROP ROW POLICY FOR ROLE role1, role2, ... to drop all row policies bound to specified roles in batch.

### Check List (For Author)

- Test: Regression test, Unit Test
- Behavior changed: Yes. New SQL syntax DROP ROW POLICY FOR ROLE supported
- Does this need documentation: Yes
@hello-stephen
Copy link
Copy Markdown
Contributor

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?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants