Re: Custom properties file for environmental promotion

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 to

Re: Custom properties file for environmental promotion

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 pu

Re: Custom properties file for environmental promotion

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/

Re: Custom properties file for environmental promotion

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. Sor

Re: Custom properties file for environmental promotion

Excellent info, as always Bryan. Very much appreciated! -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: Custom properties file for environmental promotion

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 FA

Custom properties file for environmental promotion

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 nifi.variable.regi

Re: Dynamic attributes on repeating capture groups

Sorry for the lack of response. The client decided to go a different route. I was able to get a different script running for a different application. So I think I more/less have this worked out. Thanks again! -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com

Re: Dynamic attributes on repeating capture groups

James- one last question. Does ExecuteScript support clustered NIFI instances? I keep getting this exception ONLY from the second node (2 of 2) in our cluster: "StandardFlowFileRecord ... already in use for active callback or an InputStream created by ProcessSession.read(FlowFile) has not been clo

Re: Dynamic attributes on repeating capture groups

Fantastic! Thanks for the info! -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Dynamic-attributes-on-repeating-capture-groups-tp16540p16568.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: Dynamic attributes on repeating capture groups

James- thanks for the comment. I've been hacking on this all day and think I have the python written to do what I need. I have just one follow up question as I'm new to the ExecuteScript processor. -What do I do on exception? Some of the cookbook example scripts seem to print to traceback: excep

Dynamic attributes on repeating capture groups

I am parsing a text file with semi-formatted data. I use the SplitContent processor to get me each "block" of data- basically each object, and then the ExtractText processor to get all the individual properties that will be associated to that object. So I might have a flowfile with data: foo1: ba