[
https://issues.apache.org/jira/browse/PARQUET-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625752#comment-16625752
]
James Clampffer commented on PARQUET-1422:
------------------------------------------
How about leaving pure virtual interfaces in the parquet headers and have those
use the Arrow implementations by default? It looks like doing this as
described will require more Arrow headers to be included in the build of the
core parquet library. This way parquet-core can be slimmed down without adding
new dependencies on Arrow.
> [C++] Use Arrow IO interfaces natively rather than current parquet:: wrappers
> -----------------------------------------------------------------------------
>
> Key: PARQUET-1422
> URL: https://issues.apache.org/jira/browse/PARQUET-1422
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-cpp
> Reporter: Wes McKinney
> Assignee: Wes McKinney
> Priority: Major
> Fix For: cpp-1.6.0
>
>
> We are beginning to do some work on asynchronous IO in Arrow and it would be
> great to be able to leverage this in the Parquet core internals.
> I am proposing to remove the Parquet-specific virtual file interfaces in
> https://github.com/apache/arrow/blob/master/cpp/src/parquet/util/memory.h#L221
> and instead rely directly on the Arrow ones in arrow::io. In addition to
> reducing the amount of code we have to maintain, we will also be able to
> improve performance of Parquet by utilizing common utilities for managing
> asynchronous / background IO
> cc [~mdeepak] [~xhochy]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
