Re: Review for IGNITE-4436 API to collect list of running SQL queries

2017-01-31 Thread Denis Magda
> On Jan 31, 2017, at 4:24 PM, Alexey Kuznetsov wrote: > > Denis, > >>> I would make it transparent for the user giving ability to work with > LOCAL queries as well. How difficult is to support this? > I think it not should be very hard, but I will need some help from our SQL > experts. > >>>

Re: Review for IGNITE-4436 API to collect list of running SQL queries

2017-01-31 Thread Alexey Kuznetsov
Denis, >> I would make it transparent for the user giving ability to work with LOCAL queries as well. How difficult is to support this? I think it not should be very hard, but I will need some help from our SQL experts. >> Isn’t the goal of this task to support all SQL queries? Don’t get why you

Re: Review for IGNITE-4436 API to collect list of running SQL queries

2017-01-31 Thread Denis Magda
Hi Alex, >> 1) Current implementation will collect info and cancel only "TwoStep" >> queries. >>Should we also support LOCAL queries? >> I would make it transparent for the user giving ability to work with LOCAL queries as well. How difficult is to support this? >> 2) Should we also suppor

Re: Review for IGNITE-4436 API to collect list of running SQL queries

2017-01-31 Thread Alexey Kuznetsov
Any feedback, please? On Mon, Jan 30, 2017 at 9:38 PM, Alexey Kuznetsov wrote: > Hi All! > > I prepared first version https://issues.apache.org/jira/browse/IGNITE-4436 > (SQL: create API to collect list of running SQL queries and cancel them). > > Please review it and give a feedback: http://rev

Review for IGNITE-4436 API to collect list of running SQL queries

2017-01-30 Thread Alexey Kuznetsov
Hi All! I prepared first version https://issues.apache.org/jira/browse/IGNITE-4436 (SQL: create API to collect list of running SQL queries and cancel them). Please review it and give a feedback: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-84 But also I have following questions: 1) Cur