[ARROW-3192] [Java] Implement "ArrowBufReadChannel" abstraction and alternate MessageSerializer that uses this

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Java
• External issue URL: https://github.com/apache/arrow/issues/19537
• Assignee: Unassigned
• Reporter: Wes McKinney
• Created: 07/Sep/18 20:26
• Updated: 11/Jan/23 07:25

Description

The current MessageSerializer implementation is wasteful when used to read an IPC payload that is already in-memory in an ArrowBuf. In particular, reads out of a ReadChannel require memory allocation

• https://github.com/apache/arrow/blob/master/java/vector/src/main/java/org/apache/arrow/vector/ipc/message/MessageSerializer.java#L569

• https://github.com/apache/arrow/blob/master/java/vector/src/main/java/org/apache/arrow/vector/ipc/message/MessageSerializer.java#L290

In C++, we have abstracted memory allocation out of the IPC read path so that zero-copy is possible. I suggest that a similar mechanism can be developed for Java to improve deserialization performance for in-memory messages. The new interface would return ArrowBuf when performing reads, which could be zero-copy when possible, but when not the current strategy of allocate-copy could be used