avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1309) ProtobufData does not correctly handle nested enums
Date Wed, 24 Apr 2013 00:11:16 GMT

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

Hudson commented on AVRO-1309:
------------------------------

Integrated in AvroJava #364 (See [https://builds.apache.org/job/AvroJava/364/])
    AVRO-1309. Java: Fix nested protobuf enums. (Revision 1471043)

     Result = SUCCESS
cutting : 
Files : 
* /avro/trunk/CHANGES.txt
* /avro/trunk/lang/java/protobuf/src/main/java/org/apache/avro/protobuf/ProtobufData.java
* /avro/trunk/lang/java/protobuf/src/test/java/org/apache/avro/protobuf/Test.java
* /avro/trunk/lang/java/protobuf/src/test/java/org/apache/avro/protobuf/TestProtobuf.java
* /avro/trunk/lang/java/protobuf/src/test/protobuf/test.proto

                
> ProtobufData does not correctly handle nested enums
> ---------------------------------------------------
>
>                 Key: AVRO-1309
>                 URL: https://issues.apache.org/jira/browse/AVRO-1309
>             Project: Avro
>          Issue Type: Bug
>          Components: java
>    Affects Versions: 1.7.4
>            Reporter: Steve Zesch
>            Assignee: Doug Cutting
>             Fix For: 1.7.5
>
>         Attachments: AVRO-1309.patch, cnfe_protobuf_stack_trace.txt
>
>
> When an enum is nested in several messages, a ClassNotFoundException is thrown when calling
the DataFileWriter append method. I've attached a stack trace.
> The offending line (ProtobufData.java 112):
> Class c = Class.forName(SpecificData.getClassName(s));
> Say we have an enum nested as follows (I've left out some syntax):
> {code}
> message A
>   message B
>     message C
>       enum D
> {code}
> Expected class name: org.foo.bar.A$B$C$D
> Actual class name being returned: org.foo.bar.A$D
> Only the package name, outer class, and enum class name are being taken into consideration.
All parent classes besides the outer class are ignored. Nested messages are not afflicted
by the same problem because they are resolved recursively.
> Please let me know if you require any more information or if anything is unclear.
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message