orc-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yonatan Augarten <y...@intango.com>
Subject Re: Google Protobuf Version
Date Mon, 25 Sep 2017 19:47:51 GMT
Thank you for your response - looks like it would work for us.
Would you say that it's likely that this error (*Protocol message contained
an invalid tag (zero)*) is caused by the wrong version?

On Mon, Sep 25, 2017 at 1:30 PM, Owen O'Malley <owen.omalley@gmail.com>
wrote:

> I responded on the jira (ORC-63), but the easiest fix is to use the
> "nohive" classifier that we added in ORC-174.
>
>       <dependency>
>>         <groupId>org.apache.orc</groupId>
>>         <artifactId>orc-core</artifactId>
>>         <version>1.4.0</version>
>
>        <classifier>nohive</classifier>
>
>       </dependency>
>
>
> That will shroud:
> * com.google.protobuf -> com.google.protobuf25
> * org.apache.hadoop.hive -> org.apache.orc.storage
> * org.apache.hive -> org.apache.orc.storage
>
> .. Owen
>
> On Tue, Sep 19, 2017 at 1:45 AM, Yonatan Augarten <yoni@intango.com>
> wrote:
>
>> Hello,
>>
>> Our application has a maven version conflict between protobuf 2.6.1 and
>> 2.5.0.
>> We chose to use 2.6.1, expecting backward compatibility in protobuf. This
>> has worked well for the most part, but recently we encountered corrupted
>> orc files generated by our application, and I suspect this may be the
>> reason.
>>
>> When trying to read the file, the following message was received:
>> com.google.protobuf.InvalidProtocolBufferException: Protocol message
>> contained an invalid tag (zero).
>>
>> Could this indeed be related to the protobuf version, and if so - is
>> there a plan to use the newer version for orc-core in the near future?
>>
>> Thank you
>>
>> Yoni
>>
>
>

Mime
View raw message