[THRIFT-1528] Inconsistency in optional fields between Java/C# and python

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.8
• Component/s: Python - Compiler
• Assignee: Unassigned
• Reporter: Stefan Gmeiner
• Created: 01/Mar/12 12:50
• Updated: 03/Jan/19 13:17

Description

If a struct contains optional fields with default values the generated python code serialize differently than Java or C# code.

In Java or C# optional fields are only serialized if a field was set by the client. If not the field is omited during serialization. This is possible because C#/Java maintains for each field a 'isset'-boolean which records if a field was set or not.

However the generated python code does not have such a 'isset'-structure. It writes every field which is not equal None. As the constructor initialize the optional fields with their default value, these fields are written whether they are set or not.

Issue Links

• is related to: THRIFT-3756 Improve requiredness documentation

Sub-Tasks

• C#: Inconsistency in serialization of optional fields: Closed
• Java: Inconsistency in serialization of optional fields: Open
• Delphi: Inconsistency in serialization of optional fields: Closed