[
https://issues.apache.org/jira/browse/YARN-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367594#comment-16367594
]
Haibo Chen commented on YARN-7919:
----------------------------------
Agreed, [~elserj]. My understanding of why enforcer-plugin is enabled in YARN
is, it avoids surprises (such as reported in HADOOP-13866) that come from the
breaking changes between two versions of the same dependency.
In this case, hbase depends on jcodings-1.0-18 (directly) and jcodings-1.0.13
(transitively from joni). It is probably not a real problem given both versions
are in the same 1.0.x release line. But hadoop always takes the conservative
approach. Is there any downside to make hbase-client depend on the exactly same
version, 1.0.13, of joni? It is more of a nice-to-have dependency hygiene.
Regarless, we can always work around in hadoop by explicitly overriding the
joni version
> Split timelineservice-hbase module to make YARN-7346 easier
> -----------------------------------------------------------
>
> Key: YARN-7919
> URL: https://issues.apache.org/jira/browse/YARN-7919
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineservice
> Affects Versions: 3.0.0
> Reporter: Haibo Chen
> Assignee: Haibo Chen
> Priority: Major
> Attachments: YARN-7919.00.patch, YARN-7919.01.patch,
> YARN-7919.02.patch, YARN-7919.03.patch, YARN-7919.04.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
