You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2021/09/10 14:40:00 UTC

[jira] [Updated] (IGNITE-15212) [Ignite 3] SQL API design.

     [ https://issues.apache.org/jira/browse/IGNITE-15212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey Mashenkov updated IGNITE-15212:
--------------------------------------
    Summary: [Ignite 3] SQL API design.  (was: SQL API design.)

> [Ignite 3] SQL API design.
> --------------------------
>
>                 Key: IGNITE-15212
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15212
>             Project: Ignite
>          Issue Type: New Feature
>          Components: sql
>            Reporter: Andrey Mashenkov
>            Assignee: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> We need an SQL API for executing queries, query management, and maybe other stuff like statistics management.
> Let's consider 
> # sync, async and reactive ways for query execution and compare other vendor's API.
> # potential integrations with frameworks like 
> ** Reactor - rich API for working with reactive streams [1],
> **  R2DBC - reactive analog of JDBC [2]
> **  JOOQ - query builder. [3]
> and then propose a draft of how SQL API could look like for further IEP.
> [1] https://projectreactor.io/
> [2] https://r2dbc.io/
> [3] https://www.jooq.org/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)