Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 8 May 2017 18:28:04 +0000 (UTC)
From: "Junping Du (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12679226.1384440234000.154776.1494268084934@Atlassian.JIRA>
In-Reply-To: <JIRA.12679226.1384440234000@Atlassian.JIRA>
References: <JIRA.12679226.1384440234000@Atlassian.JIRA> <JIRA.12679226.1384440234958@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HADOOP-10101) Update guava dependency to the
 latest version
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Mon, 08 May 2017 18:28:12 -0000


    [ https://issues.apache.org/jira/browse/HADOOP-10101?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16=
001262#comment-16001262 ]=20

Junping Du commented on HADOOP-10101:
-------------------------------------

Thanks [~bpodgursky] for sharing your thoughts. We are glad to hear voices =
from hadoop users as well as developers from hadoop and other related proje=
cts.

bq. The number of watchers on this ticket should be an indicator in itself,=
 and I'm sure for every person who bothered creating a jira account, there =
are a couple hundred who were bitten by this.
The number of watchers doesn't indicate they are supporting this patch but =
just they pay attention to. They have to because this patch break everythin=
g. We can bring this topic to hadoop-user alias to get more audience if nee=
ded.

bq. Has anyone contacted the maintainers on the major affected downstream p=
rojects like Spark and HBase? My guess is that they would be more than happ=
y to help work around any breakages this upgrade causes =E2=80=93 if they a=
re like us, they would be overjoyed at being able to finally upgrade.
I doubt this. I talked with several guys from HBase and Tez community offli=
ne - none of them are happy with doing the same change. That means our chan=
ge are pushing them to create/maintain branches for different version of ha=
doop (if no shading work in HADOOP-14284 which has side effect though). It =
also means the releases need to get synchronized, otherwise no downstream p=
roject release can work with Hadoop GA release will be a bigger problem.

bq. Hadoop's ancient Guava dependency is the single largest issue we run in=
to when putting any other third party jar on our client or task classpath.
Please don't blame hadoop for this. The real problem here is the poor incom=
patibility of Guava across different versions and they released 21 major ve=
rsions across 7 years. The ancient guava dependency are also suffering from=
 this.

bq. There are many libraries developed outside the Hadoop ecosystem which (=
rightfully) assume they can use a newer version of Guava, and we regularly =
either have to do horrible hacks to get these onto the client classpath, or=
 tell developers not to use them. This is an incredible time-waster that sh=
ouldn't exist.
Is there any protocol for these libraries outside of hadoop to choose an un=
iform version of guava (like version 21)? If not, bump up guava version her=
e does't help as it will still break these libraries which are using differ=
ent version. Also, there are also many apps developed within hadoop ecosyst=
em which should be seen as first class citizenship that get totally break b=
y this change. As a system software, we should have some better solution li=
ke: application classpath isolation, etc. instead of simply keeping depende=
ncy updated.

bq. I understand the concerns about stability, but this is a major upgrade,=
 no? I don't think it's acceptable to say that Hadoop will be running Guava=
 11 until Hadoop 4 comes out in 2025.
Guava is not Java, I don't think any hadoop releases should bind with speci=
fic guava version. It is just a third party library - with poor incompatibi=
lity - that's it!

> Update guava dependency to the latest version
> ---------------------------------------------
>
>                 Key: HADOOP-10101
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10101
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Rakesh R
>            Assignee: Tsuyoshi Ozawa
>              Labels: BB2015-05-TBR
>             Fix For: 3.0.0-alpha3
>
>         Attachments: HADOOP-10101-002.patch, HADOOP-10101-004.patch, HADO=
OP-10101-005.patch, HADOOP-10101-006.patch, HADOOP-10101-007.patch, HADOOP-=
10101-008.patch, HADOOP-10101-009.patch, HADOOP-10101-009.patch, HADOOP-101=
01-010.patch, HADOOP-10101-010.patch, HADOOP-10101-011.patch, HADOOP-10101.=
012.patch, HADOOP-10101.013.patch, HADOOP-10101.014.patch, HADOOP-10101.015=
.patch, HADOOP-10101.016.patch, HADOOP-10101.017.patch, HADOOP-10101.018.pa=
tch, HADOOP-10101.patch, HADOOP-10101.patch
>
>
> The existing guava version is 11.0.2 which is quite old. This issue tries=
 to update the version to as latest version as possible.=20


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org