Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!
Ok, I think I know what you mean now. Basically the GetFile is designed not to take any incoming connection as you can see in the processor documentation:
The reason such restriction applies depend on how the processor works. The GetFile is designed as a trigger processor and it executes every time a file is placed in the target path, so providing an incoming relationship (wither through routeOnAttribute or any other processor) will break this rule because that means the GetFile will only work and Get the file when upper stream processor triggers that via sending flowfile which is not what this processor is designed to do. What you need is FetchFile processor given that you know the file you are looking for because this processor takes the full file path and not just a directory.
This is RouteOnAttribute processor. As you can see I have 2 properties defined. I want to use fileTransfer property to route to GetFile processor.
And this is connection dialog box for one of the existing connections, and it lists 'fileTransfer' as a relationship.
Ok, I think I know what you mean now. Basically the GetFile is designed not to take any incoming connection as you can see in the processor documentation:
The reason such restriction applies depend on how the processor works. The GetFile is designed as a trigger processor and it executes every time a file is placed in the target path, so providing an incoming relationship (wither through routeOnAttribute or any other processor) will break this rule because that means the GetFile will only work and Get the file when upper stream processor triggers that via sending flowfile which is not what this processor is designed to do. What you need is FetchFile processor given that you know the file you are looking for because this processor takes the full file path and not just a directory.
