Description
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.
Attachments
Issue Links
- contains
-
IGNITE-5406 VisorExecutorConfiguration and VisorGridConfiguration should use IgniteConfiguration.sqlConnectorConfiguration insread of IgniteConfiguration.odbcConfiguration
- Resolved
-
IGNITE-4893 Release Ignite JDBC driver(s) under a single JAR
- Resolved
-
IGNITE-5162 Get rid of version-depended ODBC server code
- Resolved
-
IGNITE-5163 JDBC Driver: implement handshake for thin jdbc driver based on common odbc/jdbc protocol
- Resolved
-
IGNITE-5164 Rename common ODBC/JDBC classes
- Resolved
-
IGNITE-5167 ODBC: Abstract out handler and parser interfaces
- Resolved
-
IGNITE-5169 ODBC: Rework handshake to allow different handlers
- Resolved
-
IGNITE-5176 JDBC Driver: implement query execution for thin jdbc driver based on common odbc/jdbc protocol
- Resolved
-
IGNITE-5255 JDBC Driver: support DML
- Resolved
-
IGNITE-5275 Create SQL listener configuration based on OdbcConfiguration
- Resolved
-
IGNITE-5373 JDBC thin driver: improve network configuration
- Resolved
-
IGNITE-5374 JDBC/ODBC: make sure that server doesn't have idle timeout
- Resolved
-
IGNITE-5376 JDBC thin: Expose SqlFieldsQuery hints as parameters
- Resolved
-
IGNITE-5379 JDBC thin: get rid of cache name
- Resolved
-
IGNITE-5397 JDBC thin driver: clear server cursor automatically when last result piece is transmitted
- Resolved
-
IGNITE-5400 .NET: IgniteConfiguration.SqlConnectorConfiguration
- Resolved
-
IGNITE-5408 JDBC driver should not require Class.forName() call
- Resolved