I was wondering what the best practices are on making third party libraries (e.g. JDBC driver) and custom processors available to NiFi. I have read of course that storing them outside the current install is a good practice to make upgrades easier. This makes a lot of sense but what about storing them in a NAS location?
One reason for this is we have multiple servers in a cluster and to simplify the deployment of changes in the external libraries and custom properties files, it would be nice to have a single location for those resources rather than copying them to each instance. Another reason for this question is we have a cluster with 2 Windows VMs and 1 Linux VM. The path to the driver jar was entered from a Windows server as c:\... . I am going to check next whether that path can be relative to the NiFi install directory (e.g. something like ../../mylibs/driver.jar) -- View this message in context: http://apache-nifi-users-list.2361937.n4.nabble.com/NiFi-external-library-configuration-tp1919.html Sent from the Apache NiFi Users List mailing list archive at Nabble.com.
