[
https://issues.apache.org/jira/browse/HADOOP-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140260#comment-16140260
]
Daniel Templeton commented on HADOOP-14284:
-------------------------------------------
I don't like the idea of having some modules use relocated package names and
some use the original package names. I guarantee the build will be broken more
than once by careless commits. However, the goal for Hadoop 3.0 is to decouple
clients from our internal dependencies, and shading only HDFS and the YARN
clients accomplishes that goal. In the name of moving this forward, I'm
willing to go with shading only the client-consumed artifacts. We can always
come back and shade the rest in the future if we get tired of breaking the
build.
A campaign to get HDFS clients to stop using the server JARs is a grand idea,
but it doesn't absolve us from shading the server JARs, because there will be
hold-outs.
> Shade Guava everywhere
> ----------------------
>
> Key: HADOOP-14284
> URL: https://issues.apache.org/jira/browse/HADOOP-14284
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 3.0.0-alpha4
> Reporter: Andrew Wang
> Assignee: Tsuyoshi Ozawa
> Priority: Blocker
> Attachments: HADOOP-14238.pre001.patch, HADOOP-14284.002.patch,
> HADOOP-14284.004.patch, HADOOP-14284.007.patch, HADOOP-14284.010.patch,
> HADOOP-14284.012.patch
>
>
> HADOOP-10101 upgraded the guava version for 3.x to 21.
> Guava is broadly used by Java projects that consume our artifacts.
> Unfortunately, these projects also consume our private artifacts like
> {{hadoop-hdfs}}. They also are unlikely on the new shaded client introduced
> by HADOOP-11804, currently only available in 3.0.0-alpha2.
> We should shade Guava everywhere to proactively avoid breaking downstreams.
> This isn't a requirement for all dependency upgrades, but it's necessary for
> known-bad dependencies like Guava.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
