[
https://issues.apache.org/jira/browse/ARROW-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16870675#comment-16870675
]
Wes McKinney commented on ARROW-5691:
-------------------------------------
Well, the symbols have to go into some shared library, so pick your poison. My
proposed solution
* libparquet depends on libarrow
* libarrow_dataset depends on both libarrow and libparquet, and contains
arrow::csv, arrow::json, and arrow::parquet symbols, usable directly without
going through datasets API.
What other structure would you prefer? I don't think we should create a
standalone "libarrow_parquet" library.
Personally I would prefer to have a single shared library that contains all
symbols related to low level (like the current {{parquet::arrow}} symbols) and
high level (the proposed {{arrow::dataset}} APIs) interactions with file
formats. Both low- and high-level file APIs will continue to be provided
> [C++] Relocate src/parquet/arrow code to src/arrow/dataset/parquet
> ------------------------------------------------------------------
>
> Key: ARROW-5691
> URL: https://issues.apache.org/jira/browse/ARROW-5691
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Wes McKinney
> Priority: Major
> Fix For: 1.0.0
>
>
> I think it may make sense to continue developing and maintaining this code in
> the same place as other file format <-> Arrow serialization code and dataset
> handling routines (e.g. schema normalization). Under this scheme, libparquet
> becomes a link time dependency of libarrow_dataset
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
