[
https://issues.apache.org/jira/browse/YARN-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367604#comment-16367604
]
Josh Elser commented on YARN-7919:
----------------------------------
bq. 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.
Hrm, this is the part that confuses me. HBase defining a dependency on
jcoding-1.0.18 should override the transitive 1.0.13 dependency and prevent
YARN from seeing it. Is YARN setting a direct dependency on the same version of
jcodings for some reason?
> 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
