You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "James Turton (Jira)" <ji...@apache.org> on 2022/03/02 10:17:00 UTC

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

     [ https://issues.apache.org/jira/browse/DRILL-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Turton closed DRILL-8123.
-------------------------------
    Resolution: Fixed

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