[
https://issues.apache.org/jira/browse/DRILL-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Barclay (Drill) updated DRILL-2837:
------------------------------------------
Summary: Resolve Statement.cancel() really should do (was: Resolve what
JDBC's Statement.cancel() really does)
> Resolve Statement.cancel() really should do
> -------------------------------------------
>
> Key: DRILL-2837
> URL: https://issues.apache.org/jira/browse/DRILL-2837
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - JDBC
> Reporter: Daniel Barclay (Drill)
> Assignee: Daniel Barclay (Drill)
>
> It is not clear exactly what JDBC's Statement.cancel() method is supposed to
> do.
> The Javadoc method description for cancel() says only:
> "Cancels this Statement object if both the DBMS and driver support aborting
> an SQL statement. This method can be used by one thread to cancel a statement
> that is being executed by another thread."
> The JDBC PDF specification
> It seems reasonable to think that calling calling() on a Statement causes any
> associated query that has not already completed to be canceled, causes any
> associated ResultSet that is not already closed to be closed, and causes the
> statement to be closed.
> In particular, it doesn't say whether the Statement object is closed or that
> any ResultSet is closed (and doesn't actually say that the query is canceled).
> However,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
