You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/02/03 07:03:00 UTC

[jira] [Commented] (DRILL-8123) Revise scan limit pushdown

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

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

paul-rogers opened a new pull request #2450:
URL: https://github.com/apache/drill/pull/2450


   # [DRILL-8123](https://issues.apache.org/jira/browse/DRILL-8123): Revise scan limit pushdown
   
   ## Description
   
   Recent work added a push down of the limit into a scan. The work had a few holes, one of which was plugged by the recent update of EVF to manage the limit. Another hole is that the physical plan uses a value of 0 to indicate no limit, but 0 is a perfectly valid limit, it means "no data, only schema." The field name is "maxRecords", but should be "limit" to indicate the purpose.
   
   ## Documentation
   
   N/A
   
   ## Testing
   
   Reran unit tests.
   


-- 
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.

To unsubscribe, e-mail: dev-unsubscribe@drill.apache.org

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


> Revise scan limit pushdown
> --------------------------
>
>                 Key: DRILL-8123
>                 URL: https://issues.apache.org/jira/browse/DRILL-8123
>             Project: Apache Drill
>          Issue Type: New Feature
>            Reporter: Paul Rogers
>            Assignee: Paul Rogers
>            Priority: Major
>
> Recent work added a push down of the limit into a scan. The work had a few holes, one of which was plugged by the recent update of EVF to manage the limit. Another hole is that the physical plan uses a value of 0 to indicate no limit, but 0 is a perfectly valid limit, it means "no data, only schema." The field name is "maxRecords", but should be "limit" to indicate the purpose.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)