question SplitXML child/ output files getting overwritten by putFile processor in Archives of Support Questions (Read Only)

SplitXML child/ output files getting overwritten by putFile processor

deepikatechq — Thu, 19 Jul 2018 14:23:39 GMT

Hi, I am trying to use a very simple process GetFile  SplitXML  PutFile However, putfile throws error as all child files have same names and I get only one copy (first of the selected node depth data or last depending on my putFile conflict resolution strategy) I tried using updateAttribute process to change the file before sending to putFile but even that is not working. Please help.

Any suggestions on why even a simple update filename operation is not working either. Could there be any issue with some settings? I am using nifi 1.7.0

Thanks

Re: SplitXML child/ output files getting overwritten by putFile processor

MattWho — Sun, 18 Aug 2019 06:41:15 GMT

@D D

The NiFi Split type processor will produce multiple FlowFiles from a single source FlowFile. Each of those split FlowFiles produced will have the same filename assigned to them. NiFi references/keeps track of FlowFiles by a unique UUID assigned to each of them, so the fact that each has the same filename is not an issue for NiFi itself. That being said, destination systems will likely have an issue with duplicate files with the same filename.

Using the update attribute processor to change the filename on these splits is the best option here.

Creating a dynamic new property that will update the filename using the FlowFiles unique uuid is the common solution:

Thanks,

Matt

If you found this Answer addressed your original question, please take a moment to login and click "Accept" below the answer.

Re: SplitXML child/ output files getting overwritten by putFile processor

deepikatechq — Fri, 20 Jul 2018 16:15:26 GMT

Thanks a lot Matt!! It helped.

Also it turns out I was not running NiFi as administrator which was also a problem in renaming files in windows.