I knew it, because yarn depends on proto2 but my lib depends on proto3. The
reason is that proto3 runtime doesn't keep backward compatibility. The
problem can be reproduced if set option java_generate_equals_and_hash =
true with proto2.
I hope msg with proto2 still work with proto3 jar since
On Sat, Sep 5, 2015 at 9:08 PM, sam sun wrote:
> I use proto3 to log user event and then run a mapreduce to stat same
> metrics. But it reports an error:
>
> Exception in thread "Thread-2" java.lang.NoSuchMethodError:
>