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

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

shangxinli commented on pull request #901:
URL: https://github.com/apache/parquet-mr/pull/901#issuecomment-836790988


   Yeah, agree. Just one thing that sometimes it might not be straightforward 
for the user to know the exact path to manually set in the configuration for 
some deeply nested schema.  I remember last time when I worked on Avro schema, 
there are 20+ layers nested in the field and there are 'Type' in the middle 
with 'name' in it. That is not very human being readable and easy to make 
mistake. But I have less experience working on Schema, I am not certain this is 
a real issue. 
   


-- 
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:
[email protected]


> Write INT96 with parquet-avro
> -----------------------------
>
>                 Key: PARQUET-2037
>                 URL: https://issues.apache.org/jira/browse/PARQUET-2037
>             Project: Parquet
>          Issue Type: Improvement
>          Components: parquet-avro, parquet-mr
>            Reporter: Gabor Szadovszky
>            Assignee: Gabor Szadovszky
>            Priority: Major
>
> This jira is about the write path of PARQUET-1928. 
> The issue here is how to identify an Avro FIXED type that was an INT96 
> before. Of course, this feature would be behind a configuration flag 
> similarly to PARQUET-1928. But even with this flag it is not obvious to 
> differentiate a "simple" FIXED[12] byte from one that was an INT96 before.
> Two options to solve this issue:
> * Write the doc field of the avro schema that the FIXED value was an INT96.
> * Instead of implementing a configuration flag let the user specify the names 
> of the columns to be converted to INT96 via the configuration.



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

Reply via email to