[
https://issues.apache.org/jira/browse/SPARK-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352268#comment-14352268
]
Patrick Wendell commented on SPARK-5134:
----------------------------------------
Hey [~rdub] [~srowen],
As part of the 1.3 release cycle I did some more forensics on the actual
artifacts we publish. It turns out that because of the changes made for Scala
2.11 with the way our publishing works, we've actually been publishing poms
that link against Hadoop 2.2 as of Spark 1.2. And in general, the published pom
Hadoop version is decoupled now from the default one in the build itself,
because of our use of the effective pom plugin.
https://github.com/apache/spark/blob/master/dev/create-release/create-release.sh#L119
I'm actually a bit bummed that we (unintentionally) made this change in 1.2
because I do fear it likely screwed things up for some users.
But on the plus side, since we no decouple the publishing from the default
version in the pom, I don't see a big issue with updating the POM. So I
withdraw my objection on the PR.
> Bump default Hadoop version to 2+
> ---------------------------------
>
> Key: SPARK-5134
> URL: https://issues.apache.org/jira/browse/SPARK-5134
> Project: Spark
> Issue Type: Improvement
> Components: Build
> Affects Versions: 1.2.0
> Reporter: Ryan Williams
> Priority: Minor
>
> [~srowen] and I discussed bumping [the default hadoop version in the parent
> POM|https://github.com/apache/spark/blob/bb38ebb1abd26b57525d7d29703fd449e40cd6de/pom.xml#L122]
> from {{1.0.4}} to something more recent.
> There doesn't seem to be a good reason that it was set/kept at {{1.0.4}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
