drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Nadeau (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DRILL-2756) Check for cancellation in pseudo-blocking operations
Date Sun, 19 Apr 2015 01:07:58 GMT

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

Jacques Nadeau resolved DRILL-2756.
-----------------------------------
    Resolution: Fixed

Resolved as part of commit c0d5a69

> Check for cancellation in pseudo-blocking operations
> ----------------------------------------------------
>
>                 Key: DRILL-2756
>                 URL: https://issues.apache.org/jira/browse/DRILL-2756
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Relational Operators
>    Affects Versions: 0.8.0
>            Reporter: Chris Westin
>            Assignee: Jacques Nadeau
>             Fix For: 0.9.0
>
>
> Certain operators, such as hash join, hash agg, and sort, consume all of their input
before producing any output. For these, once they start working on their input, they don't
check to see if the request has been cancelled. If another fragment fails (causing the overall
query to be cancelled), or if the user requests a cancellation, these operators continue working
because they never check.
> We need to add checks (e.g., ask FragmentContext.isCancelled() or something like that)
to these at periodic points. We don't want to check after every row, but it should be checked
every so often (mimicing other operations, which generally get notified at batch boundaries).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message