[
https://issues.apache.org/jira/browse/DRILL-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486281#comment-17486281
]
ASF GitHub Bot commented on DRILL-8123:
---------------------------------------
paul-rogers commented on pull request #2450:
URL: https://github.com/apache/drill/pull/2450#issuecomment-1028704625
@jnturton, you an mark the big one as a draft. It will still contain the EVF
V2 roll-out (only), all the other stuff will be done in other PRs. Actually, I
think that one is the next one up after the two today are merged. Then, the two
readers converted to EVF V2 will follow in additional PRs. The stuff you don't
like, the date/time fixes, I'm omitting. The result is that I can't test on my
machine, so I'm letting GitHub run the tests: it must operate in the UTC time
zone.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)
