To my understanding, we are implementing JDBC batches by sending a callable to another node. If we already have a client node on the JDBC driver side, why not just issue a putAll(...) call from the client?
D. On Fri, Dec 16, 2016 at 3:02 PM, Denis Magda <dma...@apache.org> wrote: > Dmitriy, > > JDBC drivers spawns an Ignite client node and uses it for cluster > connectivity and queries execution. Queries issued over the JDBC are turned > into SqlFieldsQueries and sent to the cluster in this form. > > ODBC driver works in a bit different way. It connects to the cluster via > ODBC processor that needs to be running on one of the nodes: > https://apacheignite.readme.io/docs/odbc-driver#cluster-configuration < > https://apacheignite.readme.io/docs/odbc-driver#cluster-configuration> > > — > Denis > > > On Dec 16, 2016, at 2:41 PM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > > Igniters, > > > > Can someone explain to me how Ignite executes SQL from JDBC and ODBC > > drivers? Do we start an Ignite client node on the driver side? Or do we > use > > some other protocol to send commands to one of the Ignite nodes? > > > > Thanks, > > D. > >
