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

An exception thrown in your script and not caught will cause the process session to roll back, meaning that the flowfile will be go back to the input queue and retry. If you have the processor set to run on schedule every 0 seconds, it might retry a lot :). You are correct that routing to

Re: How to add headers to CSV file

Thanks Mark. I am almost there. Text in Flow file: ZYZTF9y wrote: > Hello, > > You should be able to do this with ReplaceText, using a Replacement > Strategy > of Prepend. The Replacement Value would then be the header that you want > to add to the > beginning of the file. > > Thanks > -Mark

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:

Re: Nifi Site-to-Site pre-existing deployments do not work after enabling TLS and Ldap

Hello, Yes, that is true. If you change the web port of the NiFi instance, it would be considered a 'new instance' in terms of Remote Process Groups. So any NiFi instance that is sending to/pulling from that instance would have to create a new Remote Process Group to point to the new URL. This

Re: How to add headers to CSV file

Hello, You should be able to do this with ReplaceText, using a Replacement Strategy of Prepend. The Replacement Value would then be the header that you want to add to the beginning of the file. Thanks -Mark > On Aug 2, 2017, at 3:36 AM, mayank rathi wrote: > > Hello