[ 
https://issues.apache.org/jira/browse/NIFI-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888790#comment-15888790
 ] 

Peter Wicks commented on NIFI-3366:
-----------------------------------

[~ggwizdz1], thanks for the contribution. Couple of thoughts, let me know what 
you think/if you'd be willing to do some additional work:

 - Make Input Folder optional, and if not present use an incoming FlowFile, 
either it's value or an attribute on it.
 - Allow for Copying along with Moving. This is a common use case I run into 
where right now I end up Putting to HDFS twice (once for HIVE ingest and once 
for Archive) where a copy would be a great second step.

Copy could be a separate ticket, but it might be nice to have a Copy/Move 
processor all in one.

Thoughts?

> MoveHDFS Processor
> ------------------
>
>                 Key: NIFI-3366
>                 URL: https://issues.apache.org/jira/browse/NIFI-3366
>             Project: Apache NiFi
>          Issue Type: New Feature
>            Reporter: Joseph Niemiec
>            Priority: Minor
>         Attachments: 0001-MoveHDFS-Processor.patch
>
>
> Today the PutHDFS Processor merely places a file into HDFS from NiFi. There 
> are times when we may want to move Files/Directories around on HDFS as part 
> of a workflow.  This could be after the PutHDFS processor has placed the 
> file, or from some other trigger. 
> Initially we are targeting to take a flow file attribute of an absolute HDFS 
> path, and be able to move it to a target HDFS Path using the Filesystem 
> RENAME API. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to