[ https://issues.apache.org/jira/browse/NIFI-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16122721#comment-16122721 ]
ASF subversion and git services commented on NIFI-4177: ------------------------------------------------------- Commit a6e8f0afe3407bf668e234dcce3c474f1ceb86c8 in nifi's branch refs/heads/master from [~makosteel] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=a6e8f0a ] NIFI-4177 This closes #2002. MergeContent - Tar - Save modification timestamp like Tar does Signed-off-by: joewitt <joew...@apache.org> > 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)