hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13687) Provide a unified dependency artifact that transitively includes the cloud storage modules shipped with Hadoop.
Date Mon, 07 Nov 2016 18:05:58 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Nauroth updated HADOOP-13687:
-----------------------------------
    Attachment: HADOOP-13687-trunk.004.patch

[~stevel@apache.org], this sounds like a good plan to me.  I think this is just a matter of
taking the branch-2 patch and applying the same thing to trunk.  I'm attaching a trunk patch
rev 004 to test that out.

I am about a week away from having access to a viable build environment for testing a rebased
HADOOP-13037 patch, so this is a good way to get the new hadoop-cloud-storage module into
place more quickly.

> Provide a unified dependency artifact that transitively includes the cloud storage modules
shipped with Hadoop.
> ---------------------------------------------------------------------------------------------------------------
>
>                 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-branch-2.002.patch,
HADOOP-13687-branch-2.003.patch, HADOOP-13687-trunk.001.patch, HADOOP-13687-trunk.002.patch,
HADOOP-13687-trunk.003.patch, HADOOP-13687-trunk.004.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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message