[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409237#comment-15409237 ] ASF GitHub Bot commented on IGNITE-1786: Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/273 > 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: odbc >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)
[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223894#comment-15223894 ] Igor Sapego commented on IGNITE-1786: - Josh, Not yet. > 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: odbc >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)
[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218721#comment-15218721 ] Joshua Nichols commented on IGNITE-1786: Is there a beta version of this ODBC driver I can download? > 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: odbc >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)
[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119011#comment-15119011 ] ASF GitHub Bot commented on IGNITE-1786: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/426 > 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: odbc >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)
[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117203#comment-15117203 ] ASF GitHub Bot commented on IGNITE-1786: GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/426 IGNITE-1786: Review-related fixes and refactoring. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-1786-review Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/426.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #426 commit 9baf2668e00ed879e7f777d0b21d58aa81c900c3 Author: isapego Date: 2016-01-25T15:17:07Z IGNITE-2447: Renamed ODBC classes to follow naming convention. commit 2a756311134e971fbfbc671f2b53090cae1085ad Author: isapego Date: 2016-01-25T15:23:20Z IGNITE-2447: Moved all ODBC classes into org.apache.ignite.internal.processors.odbc package. commit 73127efb6af2f27d75193d1a911e806ab356db94 Author: isapego Date: 2016-01-25T17:46:37Z IGNTIE-1786: Refactored according to review findings. commit e200771d597eecf537356db47915cee13b2970aa Author: isapego Date: 2016-01-25T17:58:53Z IGNITE-1786: System output replaced with logging. commit ebc6b57161ca381eeb0ed2dd97c82b5ec09c0590 Author: isapego Date: 2016-01-26T09:34:11Z IGNITE-2446: Added host property for OdbcConfiguration. commit 9abee12f0ffd98ac4137337664a066572509ed60 Author: isapego Date: 2016-01-26T10:17:34Z IGNITE-2444: Removed mentions of the VS-2014 from odbc.sln. commit f58ceb64fa3c491eaf0d38820013d29a1a54a1c6 Author: isapego Date: 2016-01-26T10:27:16Z IGNITE-2441: Fixed ToolsVersion for C++ VS projects. commit 57822b6118a2c22ee17794f32bb55e3370eb4490 Author: isapego Date: 2016-01-26T13:09:42Z IGNITE-2445: Fixed JavaDocs for ODBC. commit e8287063908ec918f5afa72032854e7bf5a54f20 Author: isapego Date: 2016-01-26T13:43:39Z IGNITE-2442: ODBC projects moved to main cpp solution. > 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: odbc >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)
[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095966#comment-15095966 ] Vladimir Ershov commented on IGNITE-1786: - Just kind reminder - we should take into account the new CacheConfiguration#setSqlSchema API and probably add a support for it. Dear QA, please check it then. > 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: odbc >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)
[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029916#comment-15029916 ] ASF GitHub Bot commented on IGNITE-1786: GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/273 IGNITE-1786: Implementation of ODBC driver for Ignite. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-1786 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/273.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #273 commit c2b5498305d3f52b519badef09b02d8988732f55 Author: isapego Date: 2015-10-27T15:25:57Z Stub for the ODBC driver commit 86104c83b96baef02bbfba7a299b9a30b9d19bef Author: isapego Date: 2015-11-05T15:00:10Z IGNITE-1786: C++ Socket client and Java ODBC server are implemented. commit 902da57e7072588975dc7df21601d256465051cb Author: isapego Date: 2015-11-09T12:54:03Z IGNTIE-1786: OdbcConfiguration for Java implemented commit f3f41441adab7a9923d9c09e7fdd2d3baa451d43 Author: isapego Date: 2015-11-10T12:51:13Z IGNITE-1786: Prepared for merge commit 22a79801c8790aebded7c565660b2550be4d270d Author: isapego Date: 2015-11-10T12:59:25Z Merge branch 'ignite-1282' into ignite-1786 commit 63054169ac3bf48e2228ed356574cc4974db4415 Author: isapego Date: 2015-11-10T13:37:53Z IGNITE-1786: move binary to separate library commit 6f279dd0c379104bb36636b1672a42af6314d641 Author: isapego Date: 2015-11-10T15:36:54Z IGNITE-1786: common and binary libs can be built now commit 92d3c7f1c40b8a3a2d7497dafda5461a74d51efd Author: isapego Date: 2015-11-10T16:14:11Z IGNITE-1786: Can be built for Windows. commit f8845c55c4bc423a407ead5b878b2b4e81c0a901 Author: isapego Date: 2015-11-10T16:55:44Z IGNITE-1786: Statement stub commit cf2dcf9598f92490579a683c145b63429180e8da Author: isapego Date: 2015-11-11T10:41:47Z IGNITE-1786: DSN Config implemented. commit 7e7ef9538804da91159dedfceedff8ccee87be4e Author: isapego Date: 2015-11-11T14:49:12Z IGNITE-1786: ApplicationDataBuffer and SQLBindCol are implemented. commit 28aaeec132b8392679cf8d65d227a2c1e08a4f8f Author: isapego Date: 2015-11-11T16:46:20Z IGNITE-1786: Query sending implemented commit 4385f5e572508b627db5fec1210b84776b2dc331 Author: isapego Date: 2015-11-11T17:02:42Z IGNITE-1786: Added protocol header stub. commit 52b8b08621c0150eb9ac5571801e2e5d928eba6c Author: isapego Date: 2015-11-11T17:45:20Z IGNITE-1786: Message receiving implemented commit 70b180de82c9cd7eb2181184033355269a9bf09f Author: isapego Date: 2015-11-11T18:07:33Z IGNITE-1786: Implemented query sending and response receiving for driver. commit e2c2b83e203093977da5f27c913965a908a646a1 Author: isapego Date: 2015-11-12T10:56:30Z IGNITE-1786: GridOdbcParser implemented. Prepared to move ODBC functionality to separate processor. commit 69557c2b92774ea695ec8c64b6eb5692df4e35f4 Author: isapego Date: 2015-11-12T17:34:28Z IGNITE-1786: Implemented GridOdbcProcessor. commit e04f1a571985e8fbf090e96a0ebdb0184ef7894d Author: isapego Date: 2015-11-13T14:23:54Z IGNITE-1786: Implmented query processing. commit 89488cad7d294828e7809050f07fb9ac159984c8 Author: isapego Date: 2015-11-16T15:55:30Z IGNITE-1786: Refactored OBDC request handling. commit 0032c12149f9e17ea36b573271766c2ed4ffd1ae Author: isapego Date: 2015-11-16T16:01:51Z IGNITE-1786: Some refactoring and preparations for fetching. commit 75ae5a03dcd9554c88051171a0bb8b89b8b1ae05 Author: isapego Date: 2015-11-16T16:23:26Z IGNITE-1786: License header added to new files. commit a9202b6a2adea238ca6881d6f30534634a390aaa Author: isapego Date: 2015-11-16T18:08:34Z IGNITE-1786: ODBC parser refactored. commit 40442fad1fbf81d41968ce02afd8caef7b780b1e Author: isapego Date: 2015-11-16T18:20:43Z IGNITE-1786: Query processing result serialisation added. commit fef62e3f0ae156b0c0b9b69cd51f0ed42e1cd7ca Author: isapego Date: 2015-11-17T15:41:13Z IGNITE-1786: Message parser implemented for driver. commit 866fecd986ebe6fb1b5d9c497feb8131e23c9867 Author: isapego Date: 2015-11-19T10:58:41Z IGNITE-1786: Info responses implemented commit e18cd8a0ec11b1e34f6cf114d4d12670aa103a47 Author: isapego Date: 2015-11-20T15:58:28Z IGNITE-1786: Implemented metadata retriving commit 5ac7772c45f82f96707dec380d2a9e4ddd840ebb Author: isapego Date: 2015-11-23T12:57:09Z IGNITE-1786: Close and unbind implemented for statement commit 651a01546f01c32f03632adfe3b4d9a67209337a Author: isapego Date: 2015-11-23T18:20:37Z IGNITE-1786: Fixed signatures of some API functions.
[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ 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)
[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[
https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976177#comment-14976177
]
Igor Sapego commented on IGNITE-1786:
-
ODBC API itself has a lot of functions. I believe it makes sense to implement
the minimum set of functions that will provide us with ability to perform
simple queries for the beginning.
Here is the set that should do:
{code}
SQLAllocHandle
SQLFreeHandle
SQLConnect
SQLDisconnect
SQLExecDirect
SQLFreeStmt
SQLFetch
SQLGetData
{code}
> 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)
[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974798#comment-14974798 ] Igor Sapego commented on IGNITE-1786: - I suggest to implement separate lightweight driver and use shared memory to communicate with the JVM. This approach will require a JVM node running on the same computer but it will be more flexible than the first approach and easier to implement than the second one. > 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)
