Skip to content

GH-1007: fix: does not break class loading if direct buffer allocator is not available#1008

Open
torito wants to merge 5 commits intoapache:mainfrom
torito:catch-jpms-failure
Open

GH-1007: fix: does not break class loading if direct buffer allocator is not available#1008
torito wants to merge 5 commits intoapache:mainfrom
torito:catch-jpms-failure

Conversation

@torito
Copy link

@torito torito commented Feb 5, 2026

What's Changed

The Direct Buffer is not always needed to use Arrow memory, however, we cannot load MemoryUtil class if we don't set:

--add-opens=java.base/java.nio=org.apache.arrow.memory.core,ALL-UNNAMED

Which is not always needed/possible.

This fix proposes to catch the InaccessibleObjectException to not avoiding the load of the class.

The directBuffer is, in any case not available and a UnsupportedOperationException will be throw as it is in the existing code

Closes #1007 .

@github-actions
Copy link

github-actions bot commented Feb 5, 2026

Thank you for opening a pull request!

Please label the PR with one or more of:

  • bug-fix
  • chore
  • dependencies
  • documentation
  • enhancement

Also, add the 'breaking-change' label if appropriate.

See CONTRIBUTING.md for details.

@torito torito marked this pull request as draft February 5, 2026 16:01
@torito torito closed this Feb 5, 2026
@torito torito reopened this Feb 5, 2026
@torito torito marked this pull request as ready for review February 5, 2026 20:17
@torito
Copy link
Author

torito commented Feb 6, 2026

I'm not able to set the bug-fix label in the PR

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.

Unable to load MemoryUtil class if we dont set --add-opens

1 participant