[Java][C++] Reorganize JNI code from several modules
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
We have several modules implementing JNI wrappers:
1. gandiva
1. plasma
1. dataset
1. orc
We can reorganize all the JNI-related codes, maybe into a single parent module, to split out the common utilities (e.g. memory pool, exception handling, reference management).
**Reporter**: [Hongze Zhang](https://issues.apache.org/jira/browse/ARROW-16691) / @zhztheplayer
**Note**: *This issue was originally created as [ARROW-16691](https://issues.apache.org/jira/browse/ARROW-16691). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start by examining the JNI wrapper code in the gandiva, plasma, dataset, and orc modules. Map the duplicated memory-pool, exception-handling, and reference-management utilities before deciding how a shared parent module should be organized. Done means the JNI code is reorganized and the common utilities are shared without losing module coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100