Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Wed, 29 Apr 2015 01:15:06 +0000 (UTC)
From: "Daniel Barclay (Drill) (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12824406.1430164810000.16264.1430270106444@Atlassian.JIRA>
In-Reply-To: <JIRA.12824406.1430164810000@Atlassian.JIRA>
References: <JIRA.12824406.1430164810000@Atlassian.JIRA>
 <JIRA.12824406.1430164810473@arcas>
Subject: [jira] [Updated] (DRILL-2884) Have cancel() cause "query canceled"
 rather than just "ResultSet closed"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Daniel Barclay (Drill) updated DRILL-2884:
------------------------------------------
    Attachment: DRILL-2884.2Hygiene.2.patch.txt

> Have cancel() cause "query canceled" rather than just "ResultSet closed"
> ------------------------------------------------------------------------
>
>                 Key: DRILL-2884
>                 URL: https://issues.apache.org/jira/browse/DRILL-2884
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Daniel Barclay (Drill)
>            Assignee: Daniel Barclay (Drill)
>         Attachments: DRILL-2884.1Core.1.patch.txt, DRILL-2884.2Hygiene.1.patch.txt, DRILL-2884.2Hygiene.2.patch.txt
>
>
> After Statement.cancel() is called for a SQL statement's execution, a subsequent call to a method on the ResultSet for that execution yields a "ResultSet already closed" exception.  (This isn't fully implemented yet, but it is for, e.g., next().)
> A call to cancel() should result in an explicit "execution canceled" exception rather than the usual "already closed" exception (so that it doesn't seem like a Drill programming error rather an expected result of canceling).


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