I don't know how difficult is something like this going to be for fixing, as the version issue can hide some other issues. It's something that needs to be investigated yet.
Now, to the versions. Yes, this is driver protocol version, which should be not higher than the node's Ignite version. It can be lower though. But please note, that after 2.1 backward compatibility for older ODBC version is going to be broken, meaning you would only be able to use new drivers with protocol version 2.1 and higher for nodes with version >= 2.1. Best Regards, Igor On Wed, Jul 26, 2017 at 3:04 PM, limabean <[email protected]> wrote: > Igor, > > Thanks for a prompt reply to this and opening a Jira for us. > > Do you have an idea on how difficult something like this is to fix ? > > Wallace and I have to support a legacy BI tool and ODBC is required to > support that tool (unfortunately). We use RazorSQL in our development > process, which is why we reported the problem when using Razor. > > Also, another question on the ODBC driver... When configuring the driver > it > offers only two options: 1.6 and 1.8. Are these versions supposed to match > the Ignite version we are connecting to (we are currently using 2.0) or > does > it matter ? > > Thanks again, > > > > > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/ODBC-version-is-not-supported-issue-tp15641p15688.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
