[Java] Check if ArrowBuf is empty buffer in getActualConsumedMemory() and getPossibleConsumedMemory()
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
Most of the methods related to memory accounting in ArrowBuf have special handling for the case when then Buffer is the empty buffer instance. This check is missing in these two methods.
**Reporter**: [Steven Phillips](https://issues.apache.org/jira/browse/ARROW-791) / @StevenMPhillips
**Note**: *This issue was originally created as [ARROW-791](https://issues.apache.org/jira/browse/ARROW-791). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start in ArrowBuf at getActualConsumedMemory() and getPossibleConsumedMemory(), comparing their empty-buffer handling with the other memory-accounting methods. Confirm the expected behavior for the empty buffer and verify both methods with the relevant ArrowBuf tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 42/100