[ https://issues.apache.org/jira/browse/PARQUET-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166971#comment-17166971 ]
Gabor Szadovszky commented on PARQUET-1684: ------------------------------------------- [~dossett], thanks a lot for the analysis. Meanwhile, on the yesterday parquet sync the community decided to not to include this one in the 1.11.1 release: {quote} The conclusion is no after the discussion. This is not a regression in Parquet11 and the change itself is not low risk. {quote} I would like to highlight that this decision was supported by the fact that parquet 1.12.0 is planned to be released soon. > [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 > Assignee: Priyank Bagrecha > Priority: Major > Labels: pull-request-available > Fix For: 1.12.0 > > Attachments: image-2020-07-28-12-24-05-087.png > > > 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)