You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Gabor Szadovszky (JIRA)" <ji...@apache.org> on 2018/04/21 12:39:05 UTC
[jira] [Updated] (PARQUET-660) Writing Protobuf messages with
extensions results in an error or data corruption.
[ https://issues.apache.org/jira/browse/PARQUET-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Szadovszky updated PARQUET-660:
-------------------------------------
Fix Version/s: 1.8.2
> Writing Protobuf messages with extensions results in an error or data corruption.
> ---------------------------------------------------------------------------------
>
> Key: PARQUET-660
> URL: https://issues.apache.org/jira/browse/PARQUET-660
> Project: Parquet
> Issue Type: Bug
> Components: parquet-mr
> Affects Versions: 1.8.1
> Reporter: Jakub Kukul
> Assignee: Jakub Kukul
> Priority: Major
> Fix For: 1.9.0, 1.8.2
>
>
> Currently, in ProtoParquetWriter there's not any support for extended protobuf messages. An attempt to write a protobuf message with extension either:
> * Results in an uninformative error like this:
> {code}
> parquet.proto.ProtoWriteSupport: Cannot write message
> YOUR_EXTENSION_TYPE cannot be cast to A_BASE_FIELD_TYPE : BASE_FIELD_NAME
> {code}
> * Results in a data corruption, if an extension type is compatible with a base field type with a corresponding index.
> Imo there are two possible solutions:
>
> 1. Ignore extension fields.
> 2. When an extension field is detected in a message, throw an informative error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)