Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

'Move Conflict Strategy' usage in FetchFile

avatar
Expert Contributor

FetchFile processor has property 'Move Conflict Strategy':

manishg_0-1710927106876.png

Basically its about file conflict in destination folder.

But it doesn't have any property for destination folder, and correctly so as this processor is only about pulling a file in nifi system.

So why is this property needed?

1 ACCEPTED SOLUTION

avatar
Super Guru

Actually there is a property called "Move Destination Directory" :

SAMSAL_0-1710928508050.png

As the description says on this properties: "this property is ignored unless the Completion Strategy is set to Move".  The same rule applies on the Move Conflict Strategy as its only considered when the Completion Strategy is set to Move . If your Completion Strategy is set to None or Delete then both properties will be ignored.

View solution in original post

1 REPLY 1

avatar
Super Guru

Actually there is a property called "Move Destination Directory" :

SAMSAL_0-1710928508050.png

As the description says on this properties: "this property is ignored unless the Completion Strategy is set to Move".  The same rule applies on the Move Conflict Strategy as its only considered when the Completion Strategy is set to Move . If your Completion Strategy is set to None or Delete then both properties will be ignored.