[ https://issues.apache.org/jira/browse/HBASE-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362697#comment-14362697 ]
Sean Busbey commented on HBASE-13149: ------------------------------------- {quote} What precisely will break when upgrade Jackson to 1.9? As long as we do not break client-server, server-server, file-formats, etc, we're good. IMHO. Specifically we can break client binary compatibility. The section about "Dependency Compatibility" is about not pulling in anything that breaks any of guarantees we just so carefully stated (my main worry there was to pull in an incompatible version of Hadoop that breaks the wire-protocol). {quote} Some downstream applications that compiled against HBase 1.0.0 will fail to compile against HBase 1.1.0. Specifically, it will be those applications that relied on the hbase-client artifact and used things that were present in jackson 1.8.8 that are no longer in 1.9 (e.g. the breaking changes mentioned in the release notes, or those that show up in the "source compatibility" tab of the jackson 1.8 to 1.9 compatibility report). > HBase MR is broken on Hadoop 2.5+ Yarn > -------------------------------------- > > Key: HBASE-13149 > URL: https://issues.apache.org/jira/browse/HBASE-13149 > Project: HBase > Issue Type: Bug > Affects Versions: 1.0.0, 2.0.0, 0.98.10.1 > Reporter: Jerry He > Priority: Critical > Attachments: HBASE-13149-0.98.patch, HBASE-13149-master.patch, > jackson-core-asl-compat_report.html, jackson-jaxrs-compat_report.html, > jackson-mapper-asl-compat_report.html, jackson-xc-compat_report.html, > jackson_1.8_to_1.9_compat_report.html > > > Running the server MR tools is not working on Yarn version 2.5+. > Running org.apache.hadoop.hbase.mapreduce.Export: > {noformat} > Exception in thread "main" java.lang.NoSuchMethodError: > org.codehaus.jackson.map.ObjectMapper.setSerializationInclusion(Lorg/codehaus/jackson/map/annotate/JsonSerialize$Inclusion;)Lorg/codehaus/jackson/map/ObjectMapper; > at > org.apache.hadoop.yarn.webapp.YarnJacksonJaxbJsonProvider.configObjectMapper(YarnJacksonJaxbJsonProvider.java:59) > at > org.apache.hadoop.yarn.util.timeline.TimelineUtils.<clinit>(TimelineUtils.java:47) > at > org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:166) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > org.apache.hadoop.mapred.ResourceMgrDelegate.<init>(ResourceMgrDelegate.java:96) > at org.apache.hadoop.mapred.YARNRunner.<init>(YARNRunner.java:112) > at > org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34) > at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95) > at org.apache.hadoop.mapreduce.Cluster.<init>(Cluster.java:82) > at org.apache.hadoop.mapreduce.Cluster.<init>(Cluster.java:75) > at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1266) > at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1262) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628) > at org.apache.hadoop.mapreduce.Job.connect(Job.java:1261) > at org.apache.hadoop.mapreduce.Job.submit(Job.java:1290) > at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1314) > at org.apache.hadoop.hbase.mapreduce.Export.main(Export.java:189) > {noformat} > The problem seems to be the jackson jar version. HADOOP-10104 updated > jackson version to 1.9.13. YARN-2092 reported a problem as well. > HBase is using jackson 1.8.8. This version of the jar in the classpath seem > to cause the problem. > Should we upgrade to jackson 1.9.13? -- This message was sent by Atlassian JIRA (v6.3.4#6332)