I'd like not to put JDBC driver jar files to nar because every database vendor has it's own JDBC driver jar file. This way service will work with any database which have JDBC compliant driver.
Don't know is NiFi lib right place for JDBC drivers, but at least this is better than in nar file. But when you can add your custom nar files to NiFi lib directory, then why not JDBC jar's? Thanks toivo -- View this message in context: http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/New-Database-Connection-Pooling-Controller-Service-tp582p842.html Sent from the Apache NiFi (incubating) Developer List mailing list archive at Nabble.com.
