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

ASF subversion and git services commented on NIFI-3366:
-------------------------------------------------------

Commit 600586d6be1ee2b7f8fb9397623a2bc8d72df1b7 in nifi's branch 
refs/heads/master from [~jtstorck]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=600586d ]

NIFI-3366 This closes #2332. Added parent/child flowfile relationship between 
the incoming flowfile and the files that are moved from the input directory to 
the output directory.
Updated to allow tests to check for evaluation of properties that support 
expression language.
Fixed bug with changeOwner attempting to operate on original file rather than 
the moved/copied file.
Added license header to MoveHDFSTest.java
Added test for moving a directory of files that contains a subdir, ensuring 
non-recursive behavior
Added to the description of the processor that it is non-recursive when a 
directory is used as input.
Added RAT exclude for test resource .dotfile to pom.xml

Signed-off-by: joewitt <[email protected]>


> MoveHDFS Processor
> ------------------
>
>                 Key: NIFI-3366
>                 URL: https://issues.apache.org/jira/browse/NIFI-3366
>             Project: Apache NiFi
>          Issue Type: New Feature
>            Reporter: Joseph Niemiec
>            Assignee: Gray Gwizdz
>            Priority: Minor
>         Attachments: 0001-MoveHDFS-Processor.patch, 
> 0001-NIFI-3366-MoveHDFS-processor-supports-expressions-la.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.4.14#64029)

Reply via email to