[
https://issues.apache.org/jira/browse/DRILL-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390840#comment-14390840
]
Chris Westin commented on DRILL-2545:
-------------------------------------
If you're killing the program, the JDBC client isn't even getting a chance to
send a cancel. The first thing to investigate is whether or not we can detect
the broken connection on the server side, and use that to cancel.
> Killing a JDBC client program does not kill the query on drillbits
> ------------------------------------------------------------------
>
> Key: DRILL-2545
> URL: https://issues.apache.org/jira/browse/DRILL-2545
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Affects Versions: 0.8.0
> Reporter: Ramana Inukonda Nagaraj
> Assignee: Chris Westin
> Fix For: 1.0.0
>
>
> Steps to repro:
> 1. Start running a query through sqlline or any JDBC app on a large dataset
> (tpch sf100)
> 2. Kill the JDBC app or sqlline.
> 3. The query still hangs around in state RUNNING through the profiles page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
