[
https://issues.apache.org/jira/browse/PARQUET-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474675#comment-15474675
]
Uwe L. Korn commented on PARQUET-712:
-------------------------------------
I would vote here to make arrow a non-optional dependency as it is a very
generic memory storage and would save us a lot of work.
> C++: Read into Arrow memory
> ---------------------------
>
> Key: PARQUET-712
> URL: https://issues.apache.org/jira/browse/PARQUET-712
> Project: Parquet
> Issue Type: New Feature
> Components: parquet-cpp
> Reporter: Uwe L. Korn
>
> We want to reverse the dependency between arrow-cpp and parquet-cpp. Thus
> parquet-cpp should depend on arrow-cpp and read/write to/from arrow memory.
> There are two options the implementation could go ahead:
> * Optionally depend on arrow-cpp and have some methods that read to arrow
> memory
> * Strictly depend on arrow-cpp: This would avoid some code duplication
> between the two projects, i.e. we could use Arrow's allocator, I/O layer,
> utility classes instead of having our own ones in parquet-cpp which do
> exactly the same, just live in another namespace.
> (I'll create some more JIRAs so we can proceed a bit more step-by-step but
> this one should be the one for coordination and discussions)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
