[
https://issues.apache.org/jira/browse/NIFI-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469509#comment-15469509
]
ASF GitHub Bot commented on NIFI-2440:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/913
Should it go into the 0.x branch:
It does not meet the criteria for backporting so doing so would require a
specific need and willing merger.
The use of ListFile statics seems ok to me personally given their highly
related nature and purpose - in this case.
I was initially concerned about the explicit use of Locale.US for the
formatter though I see we do have docs indicating that this is the case in
ListFile. Those doc lines should probably be carried forward to our writes
attributes calls here too as that format is pretty specific especially for
those who use/prefer a different locale. Ultimately we should perhaps allow it
to use whatever is the default locale for formatting on a given system though
that has its own tradeoffs.
> Add last modified time & timestamp attributes to flow files generated by
> ListSFTP processor
> -------------------------------------------------------------------------------------------
>
> Key: NIFI-2440
> URL: https://issues.apache.org/jira/browse/NIFI-2440
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Kirk Tarou
> Assignee: Joe Skora
> Priority: Trivial
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The timestamp & last modified time attributes are not exposed in ListSFTP so
> there's no way to preserve the timestamp of the remotely collected files when
> writing them out to a file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
