[
https://issues.apache.org/jira/browse/ARROW-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151756#comment-17151756
]
Bryan Cutler commented on ARROW-4526:
-------------------------------------
Thanks [~fan_li_ya] and [~rymurr] , so is one of the goals of this Jira to
remove netty as a required dependency of arrow-vector? It seems that ARROW-9300
still leaves netty-common as a dependency, but I'm not sure what references it.
Also, I'm wondering if the netty allocator is in a different module, and it's
only a dependency to arrow-vector in test scope, is it no longer the default
allocator?
> [Java] Remove Netty references from ArrowBuf and move Allocator out of vector
> package
> -------------------------------------------------------------------------------------
>
> Key: ARROW-4526
> URL: https://issues.apache.org/jira/browse/ARROW-4526
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Java
> Reporter: Jacques Nadeau
> Assignee: Liya Fan
> Priority: Critical
> Fix For: 1.0.0
>
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
