[THRIFT-772] __isset_bit_vector state before serialization differs from state after unserialization on native field

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.2
• Component/s: Java - Library
• Labels: serialization

Environment

Linux, thrift release 0.2.0 with patch Thrift-746 and Thrift-663

• Assignee: Unassigned
• Reporter: david herviou
• Created: 05/May/10 08:21
• Updated: 01/Apr/11 20:32
• Resolved: 12/May/10 23:37

Description

Once java classes have been generated it is possible to test if the fields have been set or not using the method isSetXXX().

Once one of this java class is instanciated, all call to field.isSetXXX() are returning false which is a good thing (this method ask for __isset_bit_vector.get(XXX))

Now if you serialize the previous object and unserialize it (without doing any changes on it) the following occured : all fields that corresponds to native data are returning true when isSetXXX() is invoked.

Consequently, the operation unserialise(serialize(object)) is not an identity function.

This is mainly due that the __isset_bit_vector is not serialize and rebuild during the unserialize operation.

Any idea how to fix this ?