[
https://issues.apache.org/jira/browse/ARROW-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17070919#comment-17070919
]
Ryan Murray edited comment on ARROW-8230 at 3/30/20, 12:05 PM:
---------------------------------------------------------------
Hey Liya,
I have had a look and I *think* I understand what the ticket wants, I thought
it would be useful to double check before going into implementation.
The end goal of ARROW-4526 is to remove all the dependencies on Netty from
arrow-memory. Correct?
This particular ticket is meant to create a new module (eg arrow-memory-netty)
and remove all netty dependencies from arrow-memory. arrow-memory-netty will
depend on arrow-memory but not the other way around. Does this sound roughly
correct?
At first glance there are still a few references to netty in arrow-memory,
including: ArrowBuf, BaseAllocator, BufferAllocator, BufferLedger as well as
some usages of PlatformDependent in the Hasher classes. Some of which have
already been marked Deprecated. Is the goal of this ticket to reconcile all of
these references? I assume that given the deprecated flag was added by you only
recently we only want to mark some things as deprecated rather than outright
remove them
was (Author: rymurr):
Hey Liya,
I have had a look and I *think* I understand what the ticket wants, I thought
it would be useful to double check before going into implementation.
The end goal of ARROW-4526 is to remove all the dependencies on Netty from
arrow-memory. Correct?
This particular ticket is meant to create a new module (eg arrow-memory-netty)
and remove all netty dependencies from arrow-memory. arrow-memory-netty will
depend on arrow-memory but not the other way around. Does this sound roughly
correct?
At first glance there are still a few references to netty in arrow-memory,
including: ArrowBuf, BaseAllocator, BufferAllocator, BufferLedger as well as
some usages of PlatformDependent in the Hasher classes. Is the goal of this
ticket to reconcile all of these references?
> [Java] Move Netty memory manager into a separate module
> -------------------------------------------------------
>
> Key: ARROW-8230
> URL: https://issues.apache.org/jira/browse/ARROW-8230
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Java
> Reporter: Liya Fan
> Assignee: Ryan Murray
> Priority: Major
>
> Move Netty memory manager into a separate module such that the basic
> allocator does not depend on it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)