This sounds like a good idea. Please file a JIRA and we'll get this on the roadmap. What tooling are you using, and would support for Statement.cancel() do the trick?
On Wed, Jan 27, 2016 at 7:27 PM, Ken Hampson <hamps...@gmail.com> wrote: > I would be interested in this as well, knowing how often we have had the > need in the past with similar queries on Postgres, and suspecting a similar > need as we ramp up Phoenix usage. > > - Ken > > > On Wed, Jan 27, 2016, 20:38 hongbin ma <mahong...@apache.org> wrote: > >> i'm also interested in this, allowing query killing would be nice >> >> On Wed, Jan 27, 2016 at 10:40 PM, jwilkinson <john.wilkin...@d2l.com> >> wrote: >> >>> We are interested in being able to find and kill queries that have gone >>> on >>> for a long time. >>> >>> So far, it looks like there is no way other than killing the client, and >>> no >>> way to find running queries other than to have our client track them. Is >>> that right, or have I missed something? >>> >>> In particular, I've looked at hbase tasks and found that phoenix queries >>> like "select * from bigtable" appear as many independent rpcs. >>> >>> Any insights appreciated! >>> >>> >>> >>> -- >>> View this message in context: >>> http://apache-phoenix-user-list.1124778.n5.nabble.com/Find-and-kill-long-running-queries-tp966.html >>> Sent from the Apache Phoenix User List mailing list archive at >>> Nabble.com. >>> >> >> >> >> -- >> Regards, >> >> *Bin Mahone | 马洪宾* >> Apache Kylin: http://kylin.io >> Github: https://github.com/binmahone >> >
