[jira] Commented: (THRIFT-33) Unset fields will still be serialized if they are primitives

["Stuart Sierra (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/THRIFT-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613737#action_12613737 ] 

Stuart Sierra commented on THRIFT-33:
-------------------------------------

David said: _I think that the java (without beans) code should work the same way as C++: only respect __isset if the field is marked optional._

Does that mean that C++ and (non-bean) Java code requires manually keeping __isset up to date?

> Unset fields will still be serialized if they are primitives
> ------------------------------------------------------------
>
>                 Key: THRIFT-33
>                 URL: https://issues.apache.org/jira/browse/THRIFT-33
>             Project: Thrift
>          Issue Type: Bug
>          Components: Compiler (Java), Library (Java)
>            Reporter: Bryan Duxbury
>
> Since primitive types (int, bool, byte, etc.) cannot be null in Java, the Java libraries will serialize "empty" values into their output. This is very bad when you have sparse Thrift structs with many possible fields and only one actually used. 
> The Isset logic appears to be partially implemented, but is apparently unused. It seems like the required action is using getters and setters and honoring the isset information appropriately.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.