jacques-n commented on pull request #8214: URL: https://github.com/apache/arrow/pull/8214#issuecomment-696458884
Why couldn't option 2 be done inside the vector (as opposed to in a wrapper class). ArrowBuf doesn't support reallocation (addr is final). It does allow downsizing but I'm not sure we actually need that to be implemented in arrowbuf. I'm thinking it should have been moved out when we removed the netty pattern in arrow buf. If that's the case, I'm not clear on what danger there is around buffer ownership. If ArrowBuf is addr + length locked, we should be good to calculate capacity and protect capacity on all methods that replace the buffers at the vector boundary. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
