[
https://issues.apache.org/jira/browse/HADOOP-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15550083#comment-15550083
]
Allen Wittenauer commented on HADOOP-13687:
-------------------------------------------
bq. I think your last comment is referring to HCFS implementations that reside
outside of the Apache Hadoop source tree.
Yes.
bq. The intent is not to force those to ship an artifact within Hadoop
However, the summary of this JIRA is "includes all Hadoop-compatible file
systems" ... Users who don't know any better are going to assume this really
does mean "all" if we advertise it that way. (Given how itchy folks like IBM
are about HCFS for their proprietary stuff, that isn't going to go over very
well.)
On the patch, from a build-system perspective, I think it makes more sense to
create a hadoop-hcfs dir, move the various file systems out of tools, and put
this code in there with them. This way there is a clear path of what is
expected especially if/when more file systems get added. It's also an
opportunity to pull these out of the tools dir in the distribution and actually
make them separate components. That'd make life easier in lots of ways.
> Provide a unified dependency artifact that transitively includes all
> Hadoop-compatible file systems.
> ----------------------------------------------------------------------------------------------------
>
> Key: HADOOP-13687
> URL: https://issues.apache.org/jira/browse/HADOOP-13687
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HADOOP-13687-branch-2.001.patch,
> HADOOP-13687-trunk.001.patch
>
>
> Currently, downstream projects that want to integrate with different
> Hadoop-compatible file systems like WASB and S3A need to list dependencies on
> each one. This creates an ongoing maintenance burden for those projects,
> because they need to update their build whenever a new Hadoop-compatible file
> system is introduced. This issue proposes adding a new artifact that
> transitively includes all Hadoop-compatible file systems. Similar to
> hadoop-client, this new artifact will consist of just a pom.xml listing the
> individual dependencies. Downstream users can depend on this artifact to
> sweep in everything, and picking up a new file system in a future version
> will be just a matter of updating the Hadoop dependency version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
