Thanks Bryan.
I just wrapped this up and wanted to document for anyone in the future.
-Yes, updating the kerberos principal/keytab values via the xml template
worked just fine.
-Yes, updating the target url fields on the RPG worked just fine.
-Yes, Bryan was absolutely correct that you DO need
In general that approach should work, there were a few community
efforts that did something like this in the past [1][2].
For the RPG, you may need to substitute another value as well, because
I believe the template also contains the UUID of the ports it is
connected to, which will be different
If you guys would please entertain one more question:
Unfortunately the site is currently limited to Nifi 1.2, and this
effectively renders the custom properties file useless as it relates to the
PutHDFS kerberos principal/keytab. I was thinking about this as I exported
the template in order to
Thanks Matt! I was just coming back to update. I found the 1.4 docs that
indicated that it was available there. We are currently using 1.2. I should
have researched better... Thanks again!
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
It looks like the HDFS ones were added in NiFi 1.4.0 [1] [2], and the
ListenTCP EL support for Port has an open Jira [3].
Regards,
Matt
[1] https://issues.apache.org/jira/browse/NIFI-2923
[2] https://issues.apache.org/jira/browse/NIFI-4010
[3] https://issues.apache.org/jira/browse/NIFI-4458
On
Oh no! I just realized that the Kerberos Principle and Keytab fields in
PutHDFS do *not* support expression language. Oy. This is a nonstarter...
Bryan- is there some way to submit an enhancement request for EL support on
these fields? Same goes for the port number on ListenTCP- no EL support.
Excellent info, as always Bryan. Very much appreciated!
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Currently, there is the variable properties file which would require a
service restart and also would need to be on all nodes in a cluster.
The last release (1.4.0) added a more user-friendly variable registry
in the UI which you can access from the context palette for a given
process group, near
Great info Bryan- thanks!
Regarding my first question, I talked to our admins and we only have one NIC
anyway. So there is no need for me to limit it, and thus I don't have a need
to use EL to discover the NIC. So that's good.
Regarding the registry stuff, I found this [1] document which looks
Hello,
Regarding Remote Process Groups, this is definitely something that
needs to be improved. There is a JIRA to make the URL editable [1].
A significant amount of work has been done on the flow registry [2],
and this will become the primary way to deploy flows across
environments.
The
We have nearly wrapped up our testing with out Nifi scripts in dev, and are
now looking to push to QA. I found an article about creating a custom
properties file in order to specify each of your environmental specific
variables, and then specifying that file in nifi.properties at
11 matches
Mail list logo
