Skip to content

Conversation

@github-actions
Copy link
Contributor

Cherry-picked from #59278

…#59278)

### What problem does this PR solve?
Related PR: #58936

When using JNI calls, the --add-opens parameter requires an explicit =
to ensure compatibility with modular boundaries and to correctly
interpret the relationship between modules and packages. Omitting the =
results in a JVM error (Malformed option), preventing the program from
running properly.


```
[INTERNAL_ERROR]failed to init reader, err: [JNI_ERROR]ExceptionInInitializerError: null | CAUSED BY: InaccessibleObjectException: Unable to make field private volatile java.lang.String java.net.URI.string accessible: module java.base does not "opens java.net" to unnamed module @5f565482

```

https://docs.oracle.com/en/java/javase/11/migrate/index.html#GUID-A868D0B9-026F-4D46-B979-901834343F9E

In addition, to avoid conflicts with other dependencies (e.g.,
paimon-oss), it is necessary to prioritize the loading of paimon-oss by
delegating it to the preload mechanism, ensuring consistent and stable
module loading order.
@github-actions github-actions bot requested a review from yiguolei as a code owner December 24, 2025 06:33
@hello-stephen
Copy link
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?

@dataroaring dataroaring reopened this Dec 24, 2025
@hello-stephen
Copy link
Contributor

run buildall

@hello-stephen
Copy link
Contributor

FE UT Coverage Report

Increment line coverage `` 🎉
Increment coverage report
Complete coverage report

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 53.26% (18590/34901)
Line Coverage 39.01% (172091/441167)
Region Coverage 33.69% (133041/394875)
Branch Coverage 34.69% (57539/165877)

@yiguolei yiguolei merged commit 8cdbb7c into branch-4.0 Dec 25, 2025
23 of 27 checks passed
@github-actions github-actions bot deleted the auto-pick-59278-branch-4.0 branch December 25, 2025 02:17
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.

5 participants