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 2018/05/25 20:38:00 UTC

[jira] [Commented] (DRILL-6446) Support for EMIT outcome in TopN

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

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

sohami opened a new pull request #1293: DRILL-6446: Support for EMIT outcome in TopN
URL: https://github.com/apache/drill/pull/1293
 
 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Support for EMIT outcome in TopN
> --------------------------------
>
>                 Key: DRILL-6446
>                 URL: https://issues.apache.org/jira/browse/DRILL-6446
>             Project: Apache Drill
>          Issue Type: Task
>          Components: Execution - Relational Operators
>            Reporter: Sorabh Hamirwasia
>            Assignee: Sorabh Hamirwasia
>            Priority: Major
>             Fix For: 1.14.0
>
>
> With Lateral and Unnest if TopN is present in the sub-query, then it needs to handle the EMIT outcome correctly. This means when a EMIT is received then perform the TopN operation on the records buffered so far and produce output with it. After EMIT TopN should refresh it's state and again work on next batches of incoming record unless an EMIT is seen again.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)