[Java] Remove reader index and writer index from ArrowBuf
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
Reader and writer index and functionality doesn't belong on a chunk of memory and is due to inheritance from ByteBuf. As part of removing ByteBuf inheritance, we should also remove reader and writer indexes from ArrowBuf functionality. It wastes heap memory for rare utility. In general, a slice can be used instead of a reader/writer index pattern.
**Reporter**: [Jacques Nadeau](https://issues.apache.org/jira/browse/ARROW-7494) / @jacques-n
#### PRs and other links:
- [GitHub Pull Request apache/arrow#6133](https://github.com/apache/arrow/pull/6133)
**Note**: *This issue was originally created as [ARROW-7494](https://issues.apache.org/jira/browse/ARROW-7494). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start by reading ArrowBuf and its ByteBuf inheritance to identify the reader and writer index functionality described in the issue. Trace the related API usage before deciding the scope; done means ArrowBuf no longer exposes that index functionality while the remaining buffer behavior continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100