Skip to content

branch-3.0:[test](ranger) Init ranger case#50079

Merged
dataroaring merged 3 commits intoapache:branch-3.0from
zgxme:ranger-case-0416
Apr 16, 2025
Merged

branch-3.0:[test](ranger) Init ranger case#50079
dataroaring merged 3 commits intoapache:branch-3.0from
zgxme:ranger-case-0416

Conversation

@zgxme
Copy link
Contributor

@zgxme zgxme commented Apr 16, 2025

What problem does this PR solve?

bp: #48023 #49955 #49994

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason

  • Behavior changed:

    • No.
    • Yes.

  • 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

zgxme added 3 commits April 16, 2025 10:38
@zgxme
[test](ranger) Init ranger case (apache#48023)
d70e009
@zgxme
[fix](test) Fix ranger test cases (apache#49955)
c993b3c 
### What problem does this PR solve?

1. View operations are not supported under the external catalog.
2. Update ranger masking results.

Related PR: apache#48023
@zgxme
[enhancement](ranger) modify ranger-intg to make testing more stable (a…
e385dea 
…pache#49994)

### What problem does this PR solve?
Version 3.0.0-SNAPSHOT does not work on aliyun mirror.This can cause the
CI to become unstable.

Related PR: apache#48023
@zgxme zgxme requested a review from dataroaring as a code owner April 16, 2025 02:45
@hello-stephen
Copy link
Contributor

hello-stephen commented Apr 16, 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?

@zgxme
Copy link
Contributor Author

zgxme commented Apr 16, 2025

run buildall

@github-actions
Copy link
Contributor

github-actions bot commented Apr 16, 2025

PR approved by at least one committer and no changes requested.

@github-actions github-actions bot added approved Indicates a PR has been approved by one committer. reviewed labels Apr 16, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Apr 16, 2025

PR approved by anyone and no changes requested.

dataroaring
dataroaring approved these changes Apr 16, 2025
View reviewed changes
Copy link
Contributor

@dataroaring dataroaring left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dataroaring dataroaring merged commit 9c19ac2 into apache:branch-3.0 Apr 16, 2025
23 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hello-stephen hello-stephen hello-stephen approved these changes

@dataroaring dataroaring dataroaring approved these changes

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@zgxme @hello-stephen @dataroaring