avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Carey (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1037) Problems using Avro 1.6.2 with Hadoop (CDH3 or 1.0)
Date Thu, 23 Feb 2012 22:55:49 GMT

    [ https://issues.apache.org/jira/browse/AVRO-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215157#comment-13215157

Scott Carey commented on AVRO-1037:

The stack trace I ran into was:

java.lang.NoSuchMethodError: org.codehaus.jackson.JsonNode.getValueAsDouble()D
        at org.apache.avro.Schema$Field.defaultValueEquals(Schema.java:461)
        at org.apache.avro.Schema$Field.equals(Schema.java:451)
        at java.util.AbstractList.equals(AbstractList.java:507)
        at org.apache.avro.Schema$RecordSchema.equals(Schema.java:647)
        at java.util.HashMap.put(HashMap.java:376)
> Problems using Avro 1.6.2 with Hadoop (CDH3 or 1.0)
> ---------------------------------------------------
>                 Key: AVRO-1037
>                 URL: https://issues.apache.org/jira/browse/AVRO-1037
>             Project: Avro
>          Issue Type: Bug
>          Components: java
>            Reporter: Scott Carey
>            Assignee: Scott Carey
> AVRO-972 uses a method on JsonNode that was introduced with Jackson 1.6.0.  Unfortunately,
Hadoop in a distributed environment places jackson on the mapreduce classpath prior to a user's
> Avro should function when this happens.
> There are two things we are using that are new in Jackson 1.6.0 -- JsonNode.getValueAsDouble()
 and MinimalPrettyPrinter
> MinimalPrettyPrinter is OK because the class is new, and if there is a Jackson 1.5.x
jar on a classpath before one that is >= 1.6.0, it will find the class in the second jar.
 We need to avoid JsonNode.getValueAsDouble() however.  There is a replacement that is equivalent
and existed prior, JsonNode.getDoubleValue().

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


View raw message