Re: Rethink native SQL API in Apache Ignite 2.0

2017-02-14 Thread Vladimir Ozerov
I created the ticket IGNITE-4701 [1]. Design is still be proposed. I think it is better to continue discussion here in order to involve more community members in the process. [1] https://issues.apache.org/jira/browse/IGNITE-4701 On Sat, Feb 11, 2017 at 4:04 AM, Dmitriy Setrakyan

Re: Rethink native SQL API in Apache Ignite 2.0

2017-02-10 Thread Dmitriy Setrakyan
I think the proper process here is to create a JIRA ticket and propose the design there. D. On Fri, Feb 10, 2017 at 1:37 AM, Sergi Vladykin wrote: > I agree with Vladimir that we have to improve our API with respect to the > latest changes in our SQL capabilities. > >

Re: Rethink native SQL API in Apache Ignite 2.0

2017-02-10 Thread Sergi Vladykin
I agree with Vladimir that we have to improve our API with respect to the latest changes in our SQL capabilities. As for the given API proposal, it is a bit harsh right now, but it is ok for the first draft, overall direction looks good. Also IMO we should not drop the existing API, thus adding

Re: Rethink native SQL API in Apache Ignite 2.0

2017-02-09 Thread Dmitriy Setrakyan
Vladimir, Will these changes be backward compatible? Sergi, given your SQL expertise, can you please comment here as well? D. On Tue, Feb 7, 2017 at 3:34 AM, Vladimir Ozerov wrote: > Igniters, > > Our SQL engine becomes more and more sophisticated. Initially we had only

Re: Rethink native SQL API in Apache Ignite 2.0

2017-02-07 Thread Jörn Franke
Keep in mind security, e.g. SQL injections. Ideally the API should be designed in such a way that the programmer cannot use it wrongly and allow sql injections. > On 7 Feb 2017, at 12:34, Vladimir Ozerov wrote: > > Igniters, > > Our SQL engine becomes more and more

Re: Rethink native SQL API in Apache Ignite 2.0

2017-02-07 Thread Pavel Tupitsyn
+1 SqlFieldsQuery API is quite a convoluted way to do DML. 2.0 release should certainly address this. On Tue, Feb 7, 2017 at 2:34 PM, Vladimir Ozerov wrote: > Igniters, > > Our SQL engine becomes more and more sophisticated. Initially we had only > SELECTs, now we have

Rethink native SQL API in Apache Ignite 2.0

2017-02-07 Thread Vladimir Ozerov
Igniters, Our SQL engine becomes more and more sophisticated. Initially we had only SELECTs, now we have DML, in AI 2.x we will have DDL. This is very cool, but it seems that we completely forgot about extending our native SQL API (IgniteCache.query, SqlQuery, SqlFieldsQuery) in response to