Closed drcrallen closed 1 year ago
So #2819 does not fix this yet? So far Its been impossible for me to use a JDBC lookup, same reason as the original group post. Has anyone succeeded in using them?
Sorry @MdeArcayne #2819 will have the same driver issue.
This issue has been marked as stale due to 280 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.
As per https://groups.google.com/d/msg/druid-user/3Iqi6yYG5pA/MmWDZW0BBAAJ there might be a problem in the
JDBCExtractionNamespaceFunctionFactory
whereby the JDBC driver is not registered with the DBI. It is notable thatMySQLConnector
andPostgreSQLConnector
have explicit registering of the driver in part of the constructor.A few issues arise here:
JDBCExtractionNamespaceFunctionFactory
would need a way to either A) pull from a extension config (assuming all lookups will use the same JDBC URI), or B) have a means to plug into an extension's JDBC driver registry so that different instances of namespaces can load up their drivers properly.