[
https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987044#comment-14987044
]
Igor Sapego commented on IGNITE-1786:
-------------------------------------
Ok, it seems like using a TCP sockets would be a more flexible approach. What
I'm going to do now is a walking skeleton of some kind, that will include basic
ODBC driver which can be used to connect to Ignite grid and perform some simple
queries.
Here is what I'm planning to do in the beginning:
- Add new GridNioServer to GridQueryProcessor that will communicate with the
ODBC driver.
- Add configuration for the ODBC server.
- Write a simple TCP-client on the C++ side that will work for both Windows and
Linux and that will be able to communicate with ODBC server on Java side.
- Move C++ implementation of Portable protocol to separate library.
- Use Portable protocol to send queries from C++ driver to Java and receive
responses.
> Need to implement ODBC driver for Ignite
> ----------------------------------------
>
> Key: IGNITE-1786
> URL: https://issues.apache.org/jira/browse/IGNITE-1786
> Project: Ignite
> Issue Type: New Feature
> Components: clients
> Reporter: Dmitriy Setrakyan
> Assignee: Igor Sapego
> Fix For: 1.6
>
>
> # We have a C++ API for Ignite which starts JVM internally. Probably we can
> just add that ODBC API there.
> # Another approach is to implement really separate driver and a network
> server on java side which will interact with each other.
> The first one is simpler and probably more effective, but heavyweight. The
> second one is probably slower but but more lightweight.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
