Skip to content

[fix](hdfs) remove cached file handle when read fails #54988

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
Merged
yiguolei merged 1 commit into from
Sep 12, 2025
Merged

[fix](hdfs) remove cached file handle when read fails #54988

yiguolei merged 1 commit into from
Sep 12, 2025

Conversation

@dataroaring
Copy link
Contributor

@dataroaring dataroaring commented Aug 19, 2025 •
edited
Loading

What problem does this PR solve?

pick #54926

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

None

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

@dataroaring dataroaring requested a review from yiguolei as a code owner August 19, 2025 06:58
@Thearas
Copy link
Contributor

Thearas commented Aug 19, 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
Copy link
Contributor Author

dataroaring commented Aug 19, 2025

run buildall

@hello-stephen
Copy link
Contributor

hello-stephen commented Aug 19, 2025

BE UT Coverage Report

Increment line coverage 0.00% (0/7) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 39.15% (10402/26568)
Line Coverage 30.12% (86230/286259)
Region Coverage 27.67% (49785/179918)
Branch Coverage 24.23% (24430/100808)

@github-actions
Copy link
Contributor

github-actions bot commented Sep 12, 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 Sep 12, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Sep 12, 2025

PR approved by anyone and no changes requested.

@yiguolei yiguolei merged commit ba47a4a into apache:branch-2.1 Sep 12, 2025
20 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei yiguolei 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.

4 participants

@dataroaring @Thearas @hello-stephen @yiguolei