[
https://issues.apache.org/jira/browse/NIFI-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16122686#comment-16122686
]
Joseph Witt commented on NIFI-4177:
-----------------------------------
Hello [~makosteel] Thanks for the contrib. Contrib-check/tests work out ok
still. I think we're better off not burying the exception in the event that
there is a value remaining after expression evaluation and which does not align
to the necessary format. Perhaps as a warn. However, we can come back to that
later if needed and I dont think it is worth delaying this PR and contrib as
is. Running some local tests and if checks out will merge.
thanks
> 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)
