You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2017/04/06 01:28:41 UTC

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

Denis Magda created IGNITE-4922:
-----------------------------------

             Summary: 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
            Priority: Blocker
             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)