Toivo,
You have a good point - not all drivers could be included in Apache land. One possible solution then is to have a property to configure which database you’re using and allow that to be a set of AllowableValue’s so that the user can choose any of the pre-provided choices, but also allow a “Custom” value. If they chose Custom, they would be required to provide the path to the JDBC jar. Then you would probably want to create your own instance of URLClassLoader and load the specified jar. This allows for the ease of configuring if you want to use one of the pre-loaded drivers (if any?) and allows plugability or other drivers. -Mark From: [email protected] Sent: Tuesday, February 24, 2015 1:47 PM To: [email protected] Mark, Thanks, now I understand. But at the same time would be very useful to load JDBC drivers which are not included in nar file. For example to use new JDBC version (bug fixes) or other vendor database. Or some JDBC drivers may not be open source at all (Sybase JDBC, Microsoft JDBC?) Does Oracle JDBC driver license allows to be included in NiFi? Also including many JDBC driver jar's in nar which are not mostly used increase nar size. Can NiFi have separate some sort of ext lib directory for such jar files? Because Java JDK includes Java DB (Derby version) with JDBC driver, testing can be done using this. Or Apache Derby can be also included in nar. But others? Should Postgres, MySql, etc, also included? Thanks toivo -- View this message in context: http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/New-Database-Connection-Pooling-Controller-Service-tp582p847.html Sent from the Apache NiFi (incubating) Developer List mailing list archive at Nabble.com.
