[
https://issues.apache.org/jira/browse/DRILL-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561985#comment-13561985
]
Jacques Nadeau commented on DRILL-20:
-------------------------------------
In some ways it was inspired by TOP within BigQuery combined with doing
thinking about SQL's windowing/over analytic functions. As I was going through
and doing another validation pass on the logical plan syntax after feedback
from [~julianhyde], this seemed to make sense. I'm wondering now, though, if
really this is beyond the needs of the logical plan since it could be done
through the use of a rank aggregate followed by a filter on the rank aggregate
value. On the flipside, I think it will be a while before our optimizer is
going to recognize that pattern (if ever) and it seems like a reasonably common
analytical query. [~jira.shegalov], [~julianhyde] and [~tdunning], do any of
you have any thoughts on whether segment-based limit should be a part of the
limit logical operator?
> Limit Operator Reference Implementation
> ---------------------------------------
>
> Key: DRILL-20
> URL: https://issues.apache.org/jira/browse/DRILL-20
> Project: Apache Drill
> Issue Type: Improvement
> Reporter: Chris Merrick
> Attachments: limit-reference.patch
>
>
> Build off of Jacques work on reference implementations - the limit operator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
