Toivo,
Mark,
I'm late to the conversation, but you might consider taking a look at
how the nifi-hadoop-nar depends on the nifi-hadoop-libraries-nar for
inheriting the appropriate Hadoop jars. Create a jdbc-drivers-nar
containing one or two Apache compatible JDBC driver jars. Then
someone who wants to add their JDBC driver of choice can simply
rebuild that nar after adding their JDBC driver dependency.
Then your nar inheritance structure would look something like this:
+ nifi-standard-services-api-nar
+ nifi-dbcp-service-api-nar
+ nifi-dbcp-drivers-nar
+ nifi-dbcp-service-nar
It's a bit more complicated, but we've proven that this works well
with Hadoop in NiFi.
-- Mike
On Wed, Feb 25, 2015 at 11:33 AM, Toivo Adams <[email protected]> wrote:
> Hi,
> How I can change properties dynamically?
> For example service has PropertyDescriptors:
> DATABASE_SYSTEM which contains all known databases as AllowableValue’s.
> DRIVERNAME database specific driver name, initially empty
> SERVERPORT database server specific port, initially empty
>
> When user will choose DATABASE_SYSTEM, service will catch this using
> onPropertyModified
> Now I want fill DRIVERNAME and SERVERPORT values for user, so user don’t
> need to enter them. But can change when needed.
>
> Thanks
> Toivo
>
>
>
>
> --
> View this message in context:
> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/New-Database-Connection-Pooling-Controller-Service-tp582p854.html
> Sent from the Apache NiFi (incubating) Developer List mailing list archive at
> Nabble.com.
