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

Denis Magda updated IGNITE-4701:
--------------------------------
    Description: 
Ticket is created as a result of the following discussion: 
http://apache-ignite-developers.2346864.n4.nabble.com/Rethink-native-SQL-API-in-Apache-Ignite-2-0-td14335.html

We need new SQL API which will be able to handle new SQL features such as DML, 
DDL, batching, streaming, in a clean and consistent way. Old {{Query}} API is 
not suitable for this.

Example of a usability issue the API can help to solve: 
http://apache-ignite-developers.2346864.n4.nabble.com/CREATE-TABLE-usage-from-Java-API-NET-C-td21455.html

Final API design still to be proposed.

  was:
Ticket is created as a result of the following discussion: 
http://apache-ignite-developers.2346864.n4.nabble.com/Rethink-native-SQL-API-in-Apache-Ignite-2-0-td14335.html

We need new SQL API which will be able to handle new SQL features such as DML, 
DDL, batching, streaming, in a clean and consistent way. Old {{Query}} API is 
not suitable for this.

Final API design still to be proposed.


> New SQL API 
> ------------
>
>                 Key: IGNITE-4701
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4701
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Vladimir Ozerov
>              Labels: important
>
> Ticket is created as a result of the following discussion: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Rethink-native-SQL-API-in-Apache-Ignite-2-0-td14335.html
> We need new SQL API which will be able to handle new SQL features such as 
> DML, DDL, batching, streaming, in a clean and consistent way. Old {{Query}} 
> API is not suitable for this.
> Example of a usability issue the API can help to solve: 
> http://apache-ignite-developers.2346864.n4.nabble.com/CREATE-TABLE-usage-from-Java-API-NET-C-td21455.html
> Final API design still to be proposed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to