[
https://issues.apache.org/jira/browse/PARQUET-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086405#comment-15086405
]
Nong Li commented on PARQUET-267:
---------------------------------
[~kmills] I agree, this is a big barrier to getting started. I think there are
few things we need to decide on before we pick one implementation.
I think the high level requirements are:
1. Easy to build the project out of the box. We want to minimize the steps
required from no dev environment to repo cloned, built and tests passing. This
needs to work on a large variety of environments.
2. Easy to update or add new dependencies.
This makes me lean towards *not* having the developer have maintain the build
environment by default. For someone who does a lot of c++ development and has
an existing environment they like, they should be able to use that but for
someone getting started, we should provide a "sandboxed" environment that just
works. Furthermore, the sandbox environment IMO, is the only supported one. In
other words, we can for example, upgrade to a new version of glog just by
upgrading the sandbox version. If you chose to run a custom glog that is too
old, too bad, you have to figure out how to manage your custom env.
> 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)
