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

Sean Busbey commented on HADOOP-13332:
--------------------------------------

bq. By the way wouldn't the shaded jars pull in old YARN classes as well?

The shaded hbase-server jar probably includes some YARN/MR classes since that's 
where our mapreduce integration still lives. They should be relocated to a 
location only used by the hbase code though, so they ought not conflict with 
the classes provided by yarn itself.

It would be helpful to the hbase project if you could detail why you need the 
hbase-server jar in the first place, presuming it isn't for some kind of 
mapreduce integration.

bq. Also, HBASE-13517 has a comment which says HBaseTestingUtil cannot be used 
with shaded jars, something which we use extensively in our tests.

It's true that HBaseTestingUtil is not currently compatible with the shaded 
jars. I believe we have an open jira to create a shaded version of the test jar 
that does work with them. It'd be helpful if you could ping it about the impact 
on YARN's use of HBase. (even better if you have some cycles to help complete 
it, natch.)

> Remove jackson 1.9.13 and switch all jackson code to 2.x code line
> ------------------------------------------------------------------
>
>                 Key: HADOOP-13332
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13332
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 2.8.0
>            Reporter: PJ Fanning
>            Assignee: Akira Ajisaka
>         Attachments: HADOOP-13332.00.patch, HADOOP-13332.01.patch, 
> HADOOP-13332.02.patch, HADOOP-13332.03.patch
>
>
> This jackson 1.9 code line is no longer maintained. Upgrade
> Most changes from jackson 1.9 to 2.x just involve changing the package name.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to