[ 
https://issues.apache.org/jira/browse/AVRO-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

George Baxter updated AVRO-1478:
--------------------------------

    Description: 
Utilizing the ProtobufData functionality to generate avro output, we run into a 
complication when consuming this output using the c based avro reader.  Seems 
it doesn't much like the '$' of a nesting outer class that is inherent with 
protocol buffers in java.

Exception opening file for read:Invalid namespace: 
com.xxx.base.message.MessageProtos$

in 

avro::DataFileReader<avro::GenericDatum>* file_reader;
file_reader = new avro::DataFileReader<avro::GenericDatum>(file_name.c_str());]

  was:
Utilizing the ProtobufData functionality to generate avro output, we run into a 
complication when consuming this output using the c based avro reader.  Seems 
it doesn't much like the '$' of a nesting outer class that are inherent with 
protocol buffers in java.

Exception opening file for read:Invalid namespace: 
com.xxx.base.message.MessageProtos$

in 

avro::DataFileReader<avro::GenericDatum>* file_reader;
file_reader = new avro::DataFileReader<avro::GenericDatum>(file_name.c_str());]


> protobuf namespaces causing problem for avro c reader
> -----------------------------------------------------
>
>                 Key: AVRO-1478
>                 URL: https://issues.apache.org/jira/browse/AVRO-1478
>             Project: Avro
>          Issue Type: Bug
>            Reporter: George Baxter
>
> Utilizing the ProtobufData functionality to generate avro output, we run into 
> a complication when consuming this output using the c based avro reader.  
> Seems it doesn't much like the '$' of a nesting outer class that is inherent 
> with protocol buffers in java.
> Exception opening file for read:Invalid namespace: 
> com.xxx.base.message.MessageProtos$
> in 
> avro::DataFileReader<avro::GenericDatum>* file_reader;
> file_reader = new 
> avro::DataFileReader<avro::GenericDatum>(file_name.c_str());]



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to