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

Joseph Witt commented on NIFI-4177:
-----------------------------------

+1 will merge to master.

Follow on work is likely necessary to make it more user friendly.  I setup a 
flow with list/fetch file to merge content.  I had file.lastModifiedTime set 
and also cleared out to see behavior.  Always it used the current time of the 
system rather than the file which suggests the format from ListFile by default 
wasn't sufficient for the tar needs.  We should not have to alter ListFile to 
use those timestamps of course but rather we should make it easier to specify 
the timestamp in the merge processor.  However, that can come later.  As is it 
builds/tests/and seems to do what the author intended.

> MergeContent - Tar - Save modification timestamp like Tar does
> --------------------------------------------------------------
>
>                 Key: NIFI-4177
>                 URL: https://issues.apache.org/jira/browse/NIFI-4177
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.3.0
>            Reporter: Wayne Steel
>            Assignee: Joseph Witt
>            Priority: Trivial
>             Fix For: 1.4.0
>
>
> Tar by default saves the modification timestamp of entries.
> This mainly affects file based entries so could be done on reading the 
> attribute file.lastModifiedTime, if it exists, which is written to the 
> flowfile by GetFile or ListFile processors.
> Otherwise just leave it out as it does now.
> I propose a property with the default expression ${file.lastModifiedTime} but 
> the value must resolve to a date format of "yyyy-MM-dd'T'HH:mm:ssZ". It 
> should only be enabled when MERGE_FORMAT is set to MERGE_FORMAT_TAR



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to