[
https://issues.apache.org/jira/browse/ARROW-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17309832#comment-17309832
]
Bob Tinsman commented on ARROW-7494:
------------------------------------
Great, thanks for that feedback. While perusing the two pull requests, I did
see the issue with the switched buffers, but that ML link gives me some extra
info.
I think what you're saying is to keep to the described goal of trimming down
ArrowBuf to a more focused class ("a chunk of memory"), and I think my last
approach would get most of the way there. The code that would use the proposed
IndexedArrowBuf is not a lot; so once I get to that point, I could just use
ArrowBuf.
> [Java] Remove reader index and writer index from ArrowBuf
> ---------------------------------------------------------
>
> Key: ARROW-7494
> URL: https://issues.apache.org/jira/browse/ARROW-7494
> Project: Apache Arrow
> Issue Type: Task
> Components: Java
> Reporter: Jacques Nadeau
> Assignee: Ji Liu
> Priority: Critical
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
