[jira] [Commented] (IGNITE-4922) JDBC Driver: renew thin client based solution

["Vladimir Ozerov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996449#comment-15996449 ] 

Vladimir Ozerov commented on IGNITE-4922:
-----------------------------------------

Proposed implementation plan:
1) Merge ODBC and thin driver on server side. ODBC should use {{BinaryMarshaller}}, JDBC should use {{JdkMarshaller}};
2) Introduce {{SqlListenerConfiguration}}, which will be a copy of {{OdbcConfiguration}}, deprecate the latter;
3) Implement new driver from scratch, using {{GridNioServer}} as a base.

> JDBC Driver: renew thin client based solution
> ---------------------------------------------
>
>                 Key: IGNITE-4922
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4922
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Denis Magda
>             Fix For: 2.1
>
>
> This is a parent ticket for all the activities that are intended to improve the thin client based implementation of the JDBC driver making it default one.
>  
> Refer to the corresponding discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/jdbc-vs-jdbc2-packages-td14309.html
> In a nutshell, depending on a type of a protocol to be used for the next-gen version the options are the following:
> - This type of driver might be a default driver for tools and applications that don't need transactional support. Existing REST based protocol can be used for this scenario.
> - If we want to support transactions (which is optional at the beginning) then Yakov solution (see discussion) can be applied. However, it makes sense to implement it only after MVCC is ready.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)