Start using feature enums to value (umbrella issue)
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
Proposed logic:
1. Add flag where appropriate for supports dictionary replacement if there is a possibility it can be used.
2. Only add compressed buffers when requested.
Reading should validate enums are in range AND implementation supports them.
**Reporter**: [Micah Kornfield](https://issues.apache.org/jira/browse/ARROW-9309) / @emkornfield
#### Subtasks:
- [ ] [[Java] Use feature enum](https://github.com/apache/arrow-java/issues/333)
- [ ] [[JS] Use feature enum in javascript](https://github.com/apache/arrow-js/issues/107)
- [ ] [[C++] Use feature enum](https://github.com/apache/arrow/issues/25400)
- [X] [[Rust] Use feature enum](https://github.com/apache/arrow/issues/25401)
- [ ] [[Go] Use Feature enum](https://github.com/apache/arrow-go/issues/73)
**Note**: *This issue was originally created as [ARROW-9309](https://issues.apache.org/jira/browse/ARROW-9309). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start with the linked migration documentation and the Java subtask to determine the Java-specific scope. Review how feature values are currently handled, then verify that the Java implementation uses feature enums, validates their range and support, and only adds compressed buffers when requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100