[Java] Make JniWrapper native method be public
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
The goal is to integrate Gandiva into apache Drill project. Now drill and arrow has some differences at the column in memory representation. Drill has a 2.0 plan to integrate arrow. Now I want to do some prior work to integrate arrow lib into drill project. The first thing is to make JniWrapper's package level methods be public ones. Maybe we can rename this classes as UnsafeJniWrapper like java's Unsafe class to allow others to invoke these methods directly.
So what's your opinion about this advice ? If ok , I will submit a corresponding PR.
**Reporter**: [Weijie Tong](https://issues.apache.org/jira/browse/ARROW-4819)
**Note**: *This issue was originally created as [ARROW-4819](https://issues.apache.org/jira/browse/ARROW-4819). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start by locating JniWrapper and reviewing its package-level methods and current callers. Clarify whether the scope is only making those methods public or also renaming the class to UnsafeJniWrapper; done means the agreed API is accessible to external packages and remains suitable for Gandiva and Drill integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100