[jira] [Resolved] (PARQUET-175) Allow setting of a custom protobuf class when reading parquet file using parquet-protobuf.

["Lukas Nalezenec (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PARQUET-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukas Nalezenec resolved PARQUET-175.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.8.0

Issue resolved by pull request 183
[https://github.com/apache/parquet-mr/pull/183]

> Allow setting of a custom protobuf class when reading parquet file using parquet-protobuf.
> ------------------------------------------------------------------------------------------
>
>                 Key: PARQUET-175
>                 URL: https://issues.apache.org/jira/browse/PARQUET-175
>             Project: Parquet
>          Issue Type: Improvement
>          Components: parquet-mr
>    Affects Versions: 1.6.0
>            Reporter: Lukas Nalezenec
>            Assignee: Lukas Nalezenec
>            Priority: Minor
>             Fix For: 1.8.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> ProtoReadSupport expects that parquet file header contains name of protobuffer class. It means that we can read parquet as protobuffer only if the file was written as protobuffer.
> Parquet should allow to set custom protobufer class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)