[ 
https://issues.apache.org/jira/browse/ARROW-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067575#comment-17067575
 ] 

Liya Fan edited comment on ARROW-4526 at 3/26/20, 11:38 AM:
------------------------------------------------------------

[~rymurr] Thanks for your time.
Of the 3 work items listed above, we have finished item 1 in ARROW-7935 and 
ARROW-7935. 
We are now working on item 3 (ARROW-8229, a PR will be submitted soon).

So if you are interested, maybe you can take item 2. 
I have created an issue (ARROW-8230), and please feel free to assign it to 
yourself, if you are interested :)


was (Author: fan_li_ya):
[~rymurr] Thanks for your time.
Of the 3 work items listed above, we have finished item 1 in ARROW-7905 and 
ARROW-7935. 
We are now working on item 3 (a PR will be submitted soon).

So if you are interested, maybe you can take item 2. 
I have created an issue (ARROW-8230), and please feel free to assign it to 
yourself, if you are interested :)

> [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: 0.17.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)

Reply via email to