[ https://issues.apache.org/jira/browse/PARQUET-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17103102#comment-17103102 ]
Priyank Bagrecha commented on PARQUET-1684: ------------------------------------------- protobuf introduced experimental presence flag with 3.12.0-rc-1. I tested parquet-protobuf v1.11.0 with protobuf v3.12.0-rc-1 and this is still an issue. > [parquet-protobuf] default protobuf field values are stored as nulls > -------------------------------------------------------------------- > > Key: PARQUET-1684 > URL: https://issues.apache.org/jira/browse/PARQUET-1684 > Project: Parquet > Issue Type: Bug > Components: parquet-mr > Affects Versions: 1.10.0, 1.11.0 > Reporter: George Haddad > Priority: Major > Labels: pull-request-available > > When the source is a protobuf3 message, and the target file is Parquet, all > the default values are stored in the output parquet as `{{null`}} instead of > the actual type's default value. > For example, if the field is of type `int32`, `double` or `enum` and it > hasn't been set, the parquet value is `{{null`}} instead of `0`. When the > field's type is a `string` that hasn't been set, the parquet value is > {{`null`}} instead of an empty string. -- This message was sent by Atlassian Jira (v8.3.4#803005)