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

ASF GitHub Bot commented on DRILL-7156:
---------------------------------------

arina-ielchiieva commented on issue #1836: DRILL-7156: empty parquet files 
support
URL: https://github.com/apache/drill/pull/1836#issuecomment-518183790
 
 
   @oleg-zinovev thanks for making the changes, though the situation is little 
bit awkward, since I was working on similar changes and did not know you intend 
to do them as well (https://issues.apache.org/jira/browse/DRILL-4517). Though I 
was working on reading empty parquet files but not writing them. I suggest you 
separate out writing empty parquet files into separate PR as for reading it 
might be better if my changes will be used instead: first you change metadata 
cache files and this would affect backward compatibility as well as will have 
to store more information than needed, secondly your changes does not seem to 
optimize reading complex types. What do you think?
   
 
----------------------------------------------------------------
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


> Empty Parquet is not getting created if 0 records in result
> -----------------------------------------------------------
>
>                 Key: DRILL-7156
>                 URL: https://issues.apache.org/jira/browse/DRILL-7156
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - Parquet
>            Reporter: Sayalee Bhanavase
>            Priority: Blocker
>
> I am creating parquet tables out of joins. If there is no record in join, it 
> does not create empty. table and when I reused the table my further script 
> fails. 
> Has anyone faced this issue? Any suggestion or workaround?



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to