Update, I think I can solve the problem of referencing the driver jar location through environment/server specific custom properties file. This would allow the driver jar location to be specific to the server.
I am still curious though, for resources that are truly shared across different servers, what the implications of having NiFi loading classes or properties files from a remote location. -- View this message in context: http://apache-nifi-users-list.2361937.n4.nabble.com/NiFi-external-library-configuration-tp1919p1920.html Sent from the Apache NiFi Users List mailing list archive at Nabble.com.
