[ARROW-4526] [Java] Remove Netty references from ArrowBuf and move Allocator out of vector package

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Component/s: Java
• External issue URL: https://github.com/apache/arrow/issues/21076
• Assignee: Liya Fan
• Reporter: Jacques Nadeau
• Created: 11/Feb/19 03:25
• Updated: 11/Jan/23 07:34
• Resolved: 01/Oct/20 17:45

Description

Arrow currently has a hard dependency on Netty and exposes this in public APIs. This shouldn't be the case. There could be many allocator implementations with Netty as one possible option. We should remove hard dependency between arrow-vector and Netty, instead creating a trivial allocator. ArrowBuf should probably expose an <T> T unwrap(Class<T> clazz) method instead to allow inner providers availability without a hard reference. This should also include drastically reducing the number of methods on ArrowBuf as right now it includes every method from ByteBuf but many of those are not very useful, appropriate.

This work should come after we do the simpler ARROW-3191

Issue Links

• is a parent of: ARROW-9300 [Java] Separate Netty Memory to its own module
• is a parent of: ARROW-7505 [Java] Remove Netty dependency for ArrowBuf
• is a parent of: ARROW-8229 [Java] Move ArrowBuf into the Arrow package
• is a parent of: ARROW-8230 [Java] Move Netty memory manager into a separate module
• is a parent of: ARROW-7935 [Java] Remove Netty dependency for BufferAllocator and ReferenceManager
• is blocked by: ARROW-3191 [Java] Add support for ArrowBuf to point to arbitrary memory.
• relates to: ARROW-9356 [Java] Remove Netty dependency from arrow-vector