<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Receiving java.lang.AbstractMethodError on jackson libraries in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Receiving-java-lang-AbstractMethodError-on-jackson-libraries/m-p/172913#M37577</link>
    <description>&lt;P&gt;Know this is old but I am seeing the same issue. Just curious as to whether HADOOP_USER_CLASSPATH_FIRST solved the problem? Assume so due to the thumbsup on the comment but you mentioned mapreduce.job.user.classpath.first, is that setting picked up by TEZ jobs as well and not only MR? We're running version 0.7.0 of tez and afaik no similar flag exist there (in 0.9.0 there's tez.user.classpath.first). &lt;/P&gt;&lt;P&gt;In our case we do not get this AbstractMethodError on every run so it seems that wrong class version is only picked sporadically.&lt;/P&gt;</description>
    <pubDate>Tue, 18 Sep 2018 17:50:55 GMT</pubDate>
    <dc:creator>thomas_enqvist</dc:creator>
    <dc:date>2018-09-18T17:50:55Z</dc:date>
    <item>
      <title>Receiving java.lang.AbstractMethodError on jackson libraries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Receiving-java-lang-AbstractMethodError-on-jackson-libraries/m-p/172911#M37575</link>
      <description>&lt;P&gt;I am
facing class incompatibility issue when cascading-hive job is run using TEZ on HDP
Sandbox version 2.4. jackson-mapper-asl.jar is in both hive–exec.jar(bundled)
and Hadoop lib path. Hadoop uses version 1.9.13  and hive-exec seems to
use either 1.9.10 or lower. Currently stopped using Timeline Service for TEZ to overcome the problem. any better alternative?&lt;/P&gt;&lt;P&gt;java.lang.AbstractMethodError: org.codehaus.jackson.map.AnnotationIntrospector.findSerializer(Lorg/codehaus/jackson/map/introspect/Annotated;)Ljava/lang/Object;
 at org.codehaus.jackson.map.ser.BasicSerializerFactory.findSerializerFromAnnotation(BasicSerializerFactory.java:366)
 at org.codehaus.jackson.map.ser.BeanSerializerFactory.createSerializer(BeanSerializerFactory.java:252)
 at org.codehaus.jackson.map.ser.StdSerializerProvider._createUntypedSerializer(StdSerializerProvider.java:782)
 at org.codehaus.jackson.map.ser.StdSerializerProvider._createAndCacheUntypedSerializer(StdSerializerProvider.java:735)
 at org.codehaus.jackson.map.ser.StdSerializerProvider.findValueSerializer(StdSerializerProvider.java:344)
 at org.codehaus.jackson.map.ser.StdSerializerProvider.findTypedValueSerializer(StdSerializerProvider.java:420)
 at org.codehaus.jackson.map.ser.StdSerializerProvider._serializeValue(StdSerializerProvider.java:601)
 at org.codehaus.jackson.map.ser.StdSerializerProvider.serializeValue(StdSerializerProvider.java:256)
 at org.codehaus.jackson.map.ObjectMapper.writeValue(ObjectMapper.java:1613)
 at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$EntityLogFD.writeEntities(TimelineClientImpl.java:924)
 at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$LogFDsCache.createSummaryFDAndWrite(TimelineClientImpl.java:1438)
 at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$LogFDsCache.writeSummmaryEntityLogs(TimelineClientImpl.java:1418)
 at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$LogFDsCache.writeSummaryEntityLogs(TimelineClientImpl.java:1397)
 at org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.putEntities(TimelineClientImpl.java:823)
 at org.apache.tez.dag.history.logging.ats.ATSV15HistoryLoggingService.handleEvents(ATSV15HistoryLoggingService.java:375)
 at org.apache.tez.dag.history.logging.ats.ATSV15HistoryLoggingService.access$900(ATSV15HistoryLoggingService.java:53)
 at org.apache.tez.dag.history.logging.ats.ATSV15HistoryLoggingService$1.run(ATSV15HistoryLoggingService.java:195)
 at java.lang.Thread.run(Thread.java:745)&lt;/P&gt;</description>
      <pubDate>Thu, 11 Aug 2016 19:25:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Receiving-java-lang-AbstractMethodError-on-jackson-libraries/m-p/172911#M37575</guid>
      <dc:creator>srinivas_badvel</dc:creator>
      <dc:date>2016-08-11T19:25:37Z</dc:date>
    </item>
    <item>
      <title>Re: Receiving java.lang.AbstractMethodError on jackson libraries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Receiving-java-lang-AbstractMethodError-on-jackson-libraries/m-p/172912#M37576</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/12441/srinivasbadveli.html" nodeid="12441"&gt;@Srinivas Badveli&lt;/A&gt; did you try HADOOP_USER_CLASSPATH_FIRST (mapreduce.job.user.classpath.first) which actually allow prepend user app classpath first so the desired lib can be picked up.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Aug 2016 10:51:47 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Receiving-java-lang-AbstractMethodError-on-jackson-libraries/m-p/172912#M37576</guid>
      <dc:creator>rajkumar_singh</dc:creator>
      <dc:date>2016-08-23T10:51:47Z</dc:date>
    </item>
    <item>
      <title>Re: Receiving java.lang.AbstractMethodError on jackson libraries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Receiving-java-lang-AbstractMethodError-on-jackson-libraries/m-p/172913#M37577</link>
      <description>&lt;P&gt;Know this is old but I am seeing the same issue. Just curious as to whether HADOOP_USER_CLASSPATH_FIRST solved the problem? Assume so due to the thumbsup on the comment but you mentioned mapreduce.job.user.classpath.first, is that setting picked up by TEZ jobs as well and not only MR? We're running version 0.7.0 of tez and afaik no similar flag exist there (in 0.9.0 there's tez.user.classpath.first). &lt;/P&gt;&lt;P&gt;In our case we do not get this AbstractMethodError on every run so it seems that wrong class version is only picked sporadically.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2018 17:50:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Receiving-java-lang-AbstractMethodError-on-jackson-libraries/m-p/172913#M37577</guid>
      <dc:creator>thomas_enqvist</dc:creator>
      <dc:date>2018-09-18T17:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: Receiving java.lang.AbstractMethodError on jackson libraries</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Receiving-java-lang-AbstractMethodError-on-jackson-libraries/m-p/172914#M37578</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/98165/thomasenqvist.html" nodeid="98165"&gt;@Thomas Enqvist&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Were you able to solve this sporadic issue?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Oct 2018 14:56:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Receiving-java-lang-AbstractMethodError-on-jackson-libraries/m-p/172914#M37578</guid>
      <dc:creator>rachitchauhan43</dc:creator>
      <dc:date>2018-10-25T14:56:45Z</dc:date>
    </item>
  </channel>
</rss>

