Re: [DISCUSS] Query API for Ignite 3.0

2022-05-25 Thread Andrey Gura
Andrey, there is no IEP for Java API for SQL and would be great to have it. I'll create the IEP soon. On Fri, May 20, 2022 at 1:56 PM Andrey Mashenkov wrote: > > JFYI. we have merged the initial version of SQL public API [1] and are > going to implement it in epic [2] and I've created few ticket

Re: [DISCUSS] Query API for Ignite 3.0

2022-05-20 Thread Andrey Mashenkov
JFYI. we have merged the initial version of SQL public API [1] and are going to implement it in epic [2] and I've created few tickets on this. Andey Gura, Taras Ledkov, Konstantine Orlov would you mind to share your thoughts on implementation part in some IEP? Is there IEP page created on the topi

Re: [DISCUSS] Query API for Ignite 3.0

2021-04-06 Thread Andrey Mashenkov
Hi Taras. 1. AFAIK, only Thin clients will be available in 3.0. However, yes, Native JDBC API is still "must have" on servers. 2. We won't have other projects in dependencies if possible. Unless we/they are Jigsaw compatible though. 2.1 I think it makes sense to be an R2DBC-compatible as it is

Re: [DISCUSS] Query API for Ignite 3.0

2021-04-06 Thread Ivan Daschinsky
>> The protocols are different a lot. Оf course they are different. And handlersfers, because format different. are different. But NIO server is the same. This is normal. If you meant that it was probably possible to create one handler for JDBC thin and ODBC, it would be probably possible. But is t

Re: [DISCUSS] Query API for Ignite 3.0

2021-04-06 Thread Taras Ledkov
Hi, Ivan. My comments are inline. In general about JDBC native API: I see no reasons why a user must use different query APIs on the client and on the server node (e.g. inside services or jobs). It is complicate and not user-friendly. 1.1. Thin JDBC client will be really thin: provide netwo

Re: [DISCUSS] Query API for Ignite 3.0

2021-04-06 Thread Ivan Daschinsky
Hi Taras! >> 1.1. Thin JDBC client will be really thin: provide network communication layer and transparently map to native API. But we have already this in AI 2.x >> 1.2. Thick JDBC client implementation will be trivial: start client node and open JDBC connection on the started node. We have alrea

[DISCUSS] Query API for Ignite 3.0

2021-04-06 Thread Taras Ledkov
Hi, Ignite 3.0 requires a rethinking of the query API. We have 'cache.query()' and 'SqlFieldQuery' abstractions at the Ignite 2.x native API and several JDBC implementation for clients. I propose to think about new query/SQL API for the Ignite 3.0. My vision is something like this: Ignite wil