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

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

paul-rogers commented on pull request #2026: DRILL-7330: Implement metadata 
usage for all format plugins
URL: https://github.com/apache/drill/pull/2026#discussion_r392608927
 
 

 ##########
 File path: 
exec/java-exec/src/main/java/org/apache/drill/exec/physical/impl/scan/framework/ShimBatchReader.java
 ##########
 @@ -131,6 +131,8 @@ public boolean next() {
       eof = ! reader.next();
     }
 
+    readerOrchestrator.setEof(eof);
 
 Review comment:
   Is there a need for this? The design is that EOF is indicated when:
   
   * `open()` returns false. (As in an empty file with no schema. Think blank 
CSV file.)
   * `next()` returns false with no data. (Simple EOF.)
   * `next()` returns false with data. EOF is on the next batch.
   
   Eof handling logic is built into the `ScanOperatorExec` and, in particular, 
the `ReaderState`. I worry about adding additional state that must be kept in 
sync.
   
   What is the intent here? Maybe I can help you find a solution that uses the 
existing mechanisms.
 
----------------------------------------------------------------
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]


> Implement metadata usage for text format plugin
> -----------------------------------------------
>
>                 Key: DRILL-7330
>                 URL: https://issues.apache.org/jira/browse/DRILL-7330
>             Project: Apache Drill
>          Issue Type: Sub-task
>            Reporter: Arina Ielchiieva
>            Assignee: Vova Vysotskyi
>            Priority: Major
>             Fix For: 1.18.0
>
>
> 1. Change the current group scan to leverage Schema from Metastore;
> 2. Use stats for enabling additional logical planning rules for text format 
> plugin. It will enable such optimizations as limit, filter push and so on.
> + add possibility to pass schema through schema file (using path or table 
> root), inline.
> + check for other enhancements in analyze command



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

Reply via email to