[ https://issues.apache.org/jira/browse/PARQUET-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625840#comment-16625840 ]
Wes McKinney commented on PARQUET-1422: --------------------------------------- hi [~James C] -- I am not sure how we can maintain separate virtual interfaces while taking advantage of additional IO facilities (like asynchronous buffering) that require using shared abstractions. This is a proposal to perform a net code deletion. > [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)