Skip to content

[bugfix](jnileak) should use jni util to get jni env - #66990

Merged
yiguolei merged 1 commit into
apache:branch-4.1from
yiguolei:branch-4.1
Aug 21, 2026
Merged

[bugfix](jnileak) should use jni util to get jni env#66990
yiguolei merged 1 commit into
apache:branch-4.1from
yiguolei:branch-4.1

Conversation

@yiguolei

@yiguoleiyiguolei commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

What problem does this PR solve?

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

@hello-stephen

hello-stephen commented Aug 20, 2026

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?

@yiguolei

yiguolei commented Aug 20, 2026

Copy link
Copy Markdown
ContributorAuthor

run buildall

@hello-stephen

hello-stephen commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 0.00% (0/5) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage59.02% (25303/42875)
Line Coverage43.45% (257435/592446)
Region Coverage39.45% (203871/516746)
Branch Coverage40.97% (94056/229559)

@hello-stephen

hello-stephen commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 0.00% (0/5) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage74.02% (30927/41784)
Line Coverage58.10% (341603/587992)
Region Coverage55.01% (285013/518070)
Branch Coverage55.89% (128145/229293)

@yiguolei

yiguolei commented Aug 21, 2026

Copy link
Copy Markdown
ContributorAuthor

skip buildall

@yiguolei
yiguolei merged commit 721a828 into apache:branch-4.1Aug 21, 2026
33 of 35 checks passed
@github-actions

github-actionsBot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

PR approved by anyone and no changes requested.

@github-actionsgithub-actionsBot added the approved Indicates a PR has been approved by one committer. label Aug 21, 2026
@github-actions

github-actionsBot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

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

@suxiaogang223suxiaogang223 mentioned this pull request Aug 21, 2026
Merged
@suxiaogang223suxiaogang223 mentioned this pull request Sep 1, 2026
Open
12 tasks
suxiaogang223 added a commit to suxiaogang223/doris that referenced this pull request Sep 3, 2026
@suxiaogang223
[feature](paimon) Add row-level Paimon DML
f966736
### What problem does this PR solve?
Issue Number: closeapache#65086
Related PR: apache#66990
Problem Summary: Forward-port changelog planning for Paimon DELETE, UPDATE, and MERGE statements. The planner emits row-kind plus full-row records, validates deterministic primary-key behavior for MERGE, and preserves branch evaluation with an explicit short-circuit expression.
### Release note
Support DELETE, UPDATE, and MERGE writes for Paimon tables.
### Check List (For Author)
- Test: Manual test
- FE checkstyle passed; final compilation is deferred until all forward-port picks are complete.
- Behavior changed: Yes, Paimon tables support connector row-level DML planning.
- Does this need documentation: No
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@suxiaogang223suxiaogang223suxiaogang223 approved these changes

Assignees

No one assigned

Labels

approvedIndicates 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

@yiguolei@hello-stephen@suxiaogang223