In case of a binary field, getFieldValue returns a byte while setFieldValue expects a ByteBuffer.
This design yields an unexpected requirement and is error prone.
This is a perfectly fine use-case that a client wants to write a field value from one object to another object of the same thrift generated class:
It is a reasonable assumption that if I use a getter to obtain some property value, the corresponding setter should accept a value of the same type.
Currently if SOME_FIELD is a binary type field an exception is thrown: java.lang.ClassCastException: [B cannot be cast to java.nio.ByteBuffer.
Setter setFieldValue should accept a byte value for a binary field.