[ https://issues.apache.org/jira/browse/HADOOP-8104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215001#comment-13215001 ]
Colin Patrick McCabe commented on HADOOP-8104: ---------------------------------------------- I just checked, and it seems that HBASE already uses a different version of both Jersey and Jackson. So I don't think it will be affected by this change. It's also worth noting that they have this comment: {{code}} <!-- While jackson is also a dependency of both jersey and avro, these can bring in jars from different, incompatible versions. We force the same version with these dependencies --> {{code}} By the way, I DID try adding those dependencies to HDFS, but it didn't resolve the version problem for HDFS. > Inconsistent Jackson versions > ----------------------------- > > Key: HADOOP-8104 > URL: https://issues.apache.org/jira/browse/HADOOP-8104 > Project: Hadoop Common > Issue Type: Bug > Reporter: Colin Patrick McCabe > Assignee: Colin Patrick McCabe > Attachments: HADOOP-8104.patch, dependency-tree-old.txt > > > This is a maven build issue. > Jersey 1.8 is pulling in version 1.7.1 of Jackson. Meanwhile, we are > manually specifying that we want version 1.8 of Jackson in the POM files. > This causes a conflict where Jackson produces unexpected results when > serializing Map objects. > How to reproduce: try this code: > {quote} > ObjectMapper mapper = new ObjectMapper(); > Map<String, Object> m = new HashMap<String, Object>(); > mapper.writeValue(new File("foo"), m); > {quote} > You will get an exception: > {quote} > Exception in thread "main" java.lang.NoSuchMethodError: > org.codehaus.jackson.type.JavaType.isMapLikeType()Z > at > org.codehaus.jackson.map.ser.BasicSerializerFactory.buildContainerSerializer(BasicSerializerFactory.java:396) > at > org.codehaus.jackson.map.ser.BeanSerializerFactory.createSerializer(BeanSerializerFactory.java:267) > {quote} > Basically the inconsistent versions of various Jackson components are causing > this NoSuchMethod error. > As far as I know, this only occurs when serializing maps-- that's why it > hasn't been found and fixed yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira