takbb
September 8, 2021, 8:39am
6
Hi @zhuma , Could this be similar to the issue outlined here on a different jdbc driver?
Hi Andreas,
it seems as if the Dremio driver does not support the isValid() method. You can force KNIME to use a query to test the connection validity instead of using the not supported API method. To do so open the dialog of the connector node and go to the Advanced tab. In the tab add any valid Dremio query e.g. SELECT 0 that executes successfully as value of the Validation query setting.
[image]
You might also want to check the other advanced settings to see if they are compatible with Dr…
Basically it tries to call isValid which isn’t supported by the driver, so you need to supply a validation query in the config instead. Might not be, but looks very similar to me.
I came across this same issue recently when assisting with SQL Server too… buried in here… KNIME to SQL Server - #10 by takbb
This is what I got…
That had me scratching my head, but fortunately an old post on the KNIME forum came to my rescue. This occurs when the jdbc driver doesn’t have an isvalid method (or something like that). In which case, we have to head to the config for the connector node again and open the Advanced tab, and in the “Validation query” option, type the following:
select 0
then press Apply and OK.
I don’t recall if it has to return zero, or just a value but obviously the query has to be syntactically correct for your database.
5 Likes