Thanks for your reply. We are using java for both client and sever
implementation for now. We migt use PHP for client side eventually. Both
client/sever codes are generated by thrift tool automatically. Per protocol, we
are using the Compact one.
Regarding increment to use big endian, could you share some more details about
how to do that? Thanks!
From: "Aki Sukegawa"<ns...@apache.org>
Date: 2016/10/13 01:51:34
Subject: Re: TProtocolException: Expected version 1 but got 2
Hi, what protocol do you use and against what servers/languages ?
Last time I checked, Apache Thrift against fbthrift with Compact protocol
was deemed to end up with this version 2 v.s. 1 error.
(For anyone interested/concerned, they chose to increment compact protocol
version to use big endian, rather than little endian, for double floating
point number encoding, while we chose to fix those languages that has been
erroneously using big endian.)
If you're only using Apache Thrift endpoints, it sounds worth a bug report.
On Wed, Oct 12, 2016 at 10:32 AM ???? <huaixic...@qq.com> wrote:
> I am occasionally getting below exception when using Apache Thrift:
> org.apache.thrift.protocol.TProtocolException: Expected version 1 but got 2
> I have no clue why the client is complaining about this. I am using the
> auto-gen client/server codes, and they just work in most of time. Could you
> please give me some spark on this issue?
> Appreciated any help! Thanks!