[
https://issues.apache.org/jira/browse/PHOENIX-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122378#comment-15122378
]
James Taylor commented on PHOENIX-2640:
---------------------------------------
It's possible that some kind of management UI could be built, but given our
foray into the world of tracing (which seems to have had zero community
guidance or uptake), it seems that users prefer using their own tools.
The JDBC way of killing a query is through Statement.cancel(). I'd expect
existing tooling to support canceling a query by invoking that. Phoenix is a
relatively small community, so increasing it's footprint is not necessarily
feasible (unless there are potential UI contributors that I don't know about).
My two cents is that we should look toward integration with existing tooling.
What about Apache Zeppelin?
> Make it possible to kill running queries (and ideally list them too)
> --------------------------------------------------------------------
>
> Key: PHOENIX-2640
> URL: https://issues.apache.org/jira/browse/PHOENIX-2640
> Project: Phoenix
> Issue Type: New Feature
> Reporter: John Wilkinson
>
> It would be useful to be able to find and kill queries that have gone on
> for a long time.
> Right now, it looks like there is no way other than killing the client, and no
> way to find running queries other than to have the client track them.
> One useful step would be to implement Statement.cancel(), which would allow
> client code to cleanly kill queries.
> Even better from a dev-ops/support point of view would be the ability to see
> running queries via a UI or API of some sort and kill them from there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
