Re: ODBC processor default behaviour

Denis, Good point. I'll do that. Best Regards, Igor On Tue, Nov 8, 2016 at 1:42 AM, Denis Magda wrote: > Thanks to this old discussion I was finally able to form an understanding > on how Ignite ODBC driver connects to the cluster and executes SQL queries > over it. > >

Re: ODBC processor default behaviour

Thanks to this old discussion I was finally able to form an understanding on how Ignite ODBC driver connects to the cluster and executes SQL queries over it. Igor, by some reason we didn’t add any information around ODBC processor and configuration to our documentation page. Let’s fill this

Re: ODBC processor default behaviour

I think both approaches are ok if the odbc client understands how should it deal with connection failures (should it go through a port range or retry a single port during the period of time). Sergi 2016-02-23 4:35 GMT+03:00 Valentin Kulichenko : > I think the

Re: ODBC processor default behaviour

What's about to use the port range like TcpDiscoveryVmIpFinder? On Sat, Feb 20, 2016 at 6:22 PM, Yakov Zhdanov wrote: > How about outputting warning like and keep retrying in a background thread? > > warning - "Failed to bind ODBC processor TCP server to port (retrying

Re: ODBC processor default behaviour

How about outputting warning like and keep retrying in a background thread? warning - "Failed to bind ODBC processor TCP server to port (retrying every 2 sec) [port=ABC] --Yakov 2016-02-20 17:38 GMT+03:00 Igor Sapego : > Igniters, > > I'm currently working on the ODBC

ODBC processor default behaviour

Igniters, I'm currently working on the ODBC driver. It connects by TCP to the OdbcProcessor on the node side. OdbcProcessor is enabled by default and it starts TCP server on the specific TCP port or throws exception if the port is busy. The problem is that such behavior breaks tests that start