[Java] Refactor null slot verification onto a single method in the parent class
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
After https://github.com/apache/arrow/pull/4288 is checked in there is an opportunity to refactor the code to one place instead of having the same logic across all vector classes.
**Reporter**: [Micah Kornfield](https://issues.apache.org/jira/browse/ARROW-5305) / @emkornfield
**Note**: *This issue was originally created as [ARROW-5305](https://issues.apache.org/jira/browse/ARROW-5305). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start by reviewing PR 4288, then locate the repeated null slot verification logic across the Java vector classes and identify the parent class where it should be centralized. Done means the verification has one shared implementation while preserving the existing behavior across all vector classes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100