Re: ODBC processor default behaviour

2016-11-08 Thread Igor Sapego
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. > > *Igor*, by some reason

Re: ODBC processor default behaviour

2016-11-07 Thread Denis Magda
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 ga

Re: ODBC processor default behaviour

2016-02-23 Thread Sergi Vladykin
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 behavior of OdbcProcessor should be

Re: ODBC processor default behaviour

2016-02-22 Thread Valentin Kulichenko
I think the behavior of OdbcProcessor should be consistent with RestProcessor. It tries a configurable range of ports, binds to the first available and prints it out in the log. -Val On Sat, Feb 20, 2016 at 7:33 AM, Yakov Zhdanov wrote: > Not sure if it works. DB connection string should have c

Re: ODBC processor default behaviour

2016-02-20 Thread Yakov Zhdanov
Not sure if it works. DB connection string should have certain port afaik. --Yakov 2016-02-20 18:26 GMT+03:00 Sergey Kozlov : > 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

Re: ODBC processor default behaviour

2016-02-20 Thread Sergey Kozlov
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 every > 2 sec) [port=ABC]

Re: ODBC processor default behaviour

2016-02-20 Thread Yakov Zhdanov
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 driver. It connects by TCP