[
https://issues.apache.org/jira/browse/PARQUET-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083409#comment-15083409
]
Kalon Mills commented on PARQUET-267:
-------------------------------------
[~nongli] or whoever might be maintaining this now days. I think the first
hurdle to approaching parquet-cpp right now is the build config. There are now
three pull requests on the github repo updating this. It would be great to get
one of the merged so that others don't keep reimplementing the same workarounds.
> Relax Third Party Dependency Restrictions
> -----------------------------------------
>
> Key: PARQUET-267
> URL: https://issues.apache.org/jira/browse/PARQUET-267
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-cpp
> Reporter: Kalon Mills
> Priority: Minor
>
> The existing repo has source code for third party dependencies checked into
> the repo. The build system expects those dependencies in a certain place.
> This enforces that the built library conform to those exact dependencies
> without customization.
> Managing third party dependencies is better handled through a build
> environment. It allows the library builder more flexibility over dependency
> versions and locations. It also cleans up the repo from this third party
> code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
