[ 
https://issues.apache.org/jira/browse/PARQUET-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134247#comment-17134247
 ] 

ASF GitHub Bot commented on PARQUET-1020:
-----------------------------------------

alexcardell commented on pull request #414:
URL: https://github.com/apache/parquet-mr/pull/414#issuecomment-643289745


   This PR seems to have stagnated but this is exactly what we're looking for, 
if I fork and fix those conflicts can we reignite the discussion?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Add support for Dynamic Messages in parquet-protobuf
> ----------------------------------------------------
>
>                 Key: PARQUET-1020
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1020
>             Project: Parquet
>          Issue Type: New Feature
>            Reporter: Alex Buck
>            Assignee: Alex Buck
>            Priority: Major
>
> Hello. We would like to pass in a DynamicMessage rather than using the 
> generated protobuf classes to allow us to make our job very generic. 
> I think this could be achieved by setting the descriptor upfront, similarly 
> to how there is a ProtoParquetOutputFormat today.
> In ProtoWriteSupport in the init method it could then generate the parquet 
> schema created by ProtoSchemaConverter using the passed in descriptor, rather 
> than taking it from the generated proto class.
> Would there be interest in incorporating this change? If so does the approach 
> above sound sensible? I am happy to do a pull request
> initial PR here: https://github.com/apache/parquet-mr/pull/414



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to