[
https://issues.apache.org/jira/browse/DRILL-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706607#comment-15706607
]
Julian Hyde commented on DRILL-4455:
------------------------------------
[~jnadeau], [~sphillips], [~amansinha100] and [~parthc],
Can all parties please agree (and state publicly for the record) that moving
value vector code out of Drill and into Arrow is in the best interests of the
Drill project?
Most contributions can be managed by a process of submitting a patch, review,
reject, revise, and repeat. But this is not one of those patches that can be
casually kicked back to the contributor. It is a huge, because it is an
architectural change. I would like to see a commitment from both sides
(contributor and reviewer) that we will find consensus and accept the patch.
> Depend on Apache Arrow for Vector and Memory
> --------------------------------------------
>
> Key: DRILL-4455
> URL: https://issues.apache.org/jira/browse/DRILL-4455
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Steven Phillips
> Assignee: Steven Phillips
> Fix For: 2.0.0
>
>
> The code for value vectors and memory has been split and contributed to the
> apache arrow repository. In order to help this project advance, Drill should
> depend on the arrow project instead of internal value vector code.
> This change will require recompiling any external code, such as UDFs and
> StoragePlugins. The changes will mainly just involve renaming the classes to
> the org.apache.arrow namespace.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
