The error seems to suggest you are using a different version for protoc and
protobuf Java runtime. Could you check whether they are of the same version?
On Thu, Apr 16, 2015 at 3:29 AM, Tristan Soriano mtr.sori...@gmail.com
wrote:
Hi,
I am new to protobufers and I have some issues with the
Hi,
I am new to protobufers and I have some issues with the generated java code.
I am successfully generating a java class from the following .proto file :
option java_package =
Hello,
At my current company we're heavy protobuf users, but we started
facing a big limitation: in the current Java implementation, since
there's no lazy parsing, or ability to do direct sub-message parsing,
we pay a huge penalty of time and, especially, memory (we have an
articulated schema and
On Wed, Apr 15, 2015 at 9:56 PM, Gianluca Borello g.bore...@gmail.com
wrote:
Hello,
At my current company we're heavy protobuf users, but we started
facing a big limitation: in the current Java implementation, since
there's no lazy parsing, or ability to do direct sub-message parsing,
we
On Thu, Apr 16, 2015 at 4:55 PM, Gianluca Borello g.bore...@gmail.com
wrote:
On Thu, Apr 16, 2015 at 2:08 PM, Feng Xiao xiaof...@google.com wrote:
It's either already working for Java, or only requires small tweaks for
it
to work. Could you check if marking a field lazy makes any
On Thu, Apr 16, 2015 at 5:01 PM, Feng Xiao xiaof...@google.com wrote:
Lazy does not affect the wire format. It doesn't even affect the generated
API. What happens should be that, when the Java side receives the data from
the C++ side, it will store lazy fields in a LazyField class where the
