[ 
https://issues.apache.org/jira/browse/YARN-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366904#comment-16366904
 ] 

Rohith Sharma K S commented on YARN-7919:
-----------------------------------------

I added jcodings artifact in exclusion list in 
hadoop-yarn-server-timelineservice-hbase-client/pom.xml for hbase-client 
dependency and able to compile this module in both HBase versions i.e 
HBaes-1.2.6 and Hbase-2.0-beta1. And for HBase-2.0-beta1 failed at 
hadoop-yarn-server-timelineservice-hbase-server module which is expected as 
long we fix YARN-7346.

jcodings-1.0.8.jar used to be in dependent library for hbase-client in 
hbase-1.2.6 version. It used to be shipped in timelineservice/lib folder. But 
after this change, I do not see jcoding jar in timelineservice/lib folder when 
we generate hadoop tar.gz. 

My concern is does this jar really required for hbase-client or we can go ahead 
excluding this jar for hbase-1.2.6 version! Does it going to cause 
functionality impact? 

nit : I see that package hadoop-yarn-server-timelineservice-hbase-common name 
is given as {{Apache Hadoop YARN TimelineService HBase Schema}}. I think we can 
keep name as same as module name i.e {{Apache Hadoop YARN TimelineService HBase 
Common}}.

> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to