You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Jacques Nadeau (JIRA)" <ji...@apache.org> on 2014/06/09 08:49:31 UTC
[jira] [Updated] (DRILL-641) Better semantic and handling for
kill()
[ https://issues.apache.org/jira/browse/DRILL-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Nadeau updated DRILL-641:
---------------------------------
Fix Version/s: Future
> Better semantic and handling for kill()
> ---------------------------------------
>
> Key: DRILL-641
> URL: https://issues.apache.org/jira/browse/DRILL-641
> Project: Apache Drill
> Issue Type: Improvement
> Reporter: Mehant Baid
> Fix For: Future
>
>
> Currently when an operator invokes kill(), only the upstream operators within that fragment get terminated. This causes problems if the upstream operator in a different fragment is still continuously producing batches, and it then becomes the responsibility of the operator to drain all the batches even though a kill was issued.
> While dealing with plans with multiple fragments we would need to inform the sender that a kill has been invoked. It would then be the responsibility of the sender to not push any more batches to the corresponding receiver.
--
This message was sent by Atlassian JIRA
(v6.2#6252)