[
https://issues.apache.org/jira/browse/HIVE-20687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639083#comment-16639083
]
Ashutosh Chauhan commented on HIVE-20687:
-----------------------------------------
Sounds like a good approach. One thing I am not sure is whether close() is
called on RecordReader when hive query is cancelled. I think we call close() on
tez job(dag) when query is canceled which internally might be calling close()
on RecordReader, but will be good to check.
> Cancel Running Druid Query when a hive query is cancelled.
> -----------------------------------------------------------
>
> Key: HIVE-20687
> URL: https://issues.apache.org/jira/browse/HIVE-20687
> Project: Hive
> Issue Type: Improvement
> Components: Druid integration
> Reporter: Nishant Bangarwa
> Assignee: Nishant Bangarwa
> Priority: Major
>
> https://issues.apache.org/jira/browse/HIVE-20686 ensures that hive query id
> is passed to druid.
> Druid also supports query cancellation by query id.
> Queries can be cancelled explicitly using their queryId by sending a DELETE
> request to following endpoint on the broker or router -
> {code}
> DELETE /druid/v2/{queryId}
> {code}
> Implementation wise we need to cancel a druid query when a RecordReader is
> closed.
> I believe Hive should already be calling close on open recordReaders when
> someone cancels a query.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
