[jira] [Updated] (NIFI-4177) MergeContent - Tar - Save modification timestamp like Tar does

2017-08-10 Thread Joseph Witt (JIRA) 

 [ 
https://issues.apache.org/jira/browse/NIFI-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Witt updated NIFI-4177:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> 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 "-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)

[jira] [Updated] (NIFI-4177) MergeContent - Tar - Save modification timestamp like Tar does

2017-07-12 Thread Wayne Steel (JIRA) 

 [ 
https://issues.apache.org/jira/browse/NIFI-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wayne Steel updated NIFI-4177:
--
Status: Patch Available  (was: Open)

> 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
>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 "-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)

[jira] [Updated] (NIFI-4177) MergeContent - Tar - Save modification timestamp like Tar does

2017-07-12 Thread Wayne Steel (JIRA) 

 [ 
https://issues.apache.org/jira/browse/NIFI-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wayne Steel updated NIFI-4177:
--
Flags: Patch
Fix Version/s: 1.4.0
  Component/s: Extensions

> 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
>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 "-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)

[jira] [Updated] (NIFI-4177) MergeContent - Tar - Save modification timestamp like Tar does

2017-07-12 Thread Wayne Steel (JIRA) 

 [ 
https://issues.apache.org/jira/browse/NIFI-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wayne Steel updated NIFI-4177:
--
Description: 
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 "-MM-dd'T'HH:mm:ssZ". It should 
only be enabled when MERGE_FORMAT is set to MERGE_FORMAT_TAR

  was:
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 "-MM-dd'T'HH:mm:ssZ". It should 
only be visible and enabled when MERGE_FORMAT is set to MERGE_FORMAT_TAR


> 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
>Affects Versions: 1.3.0
>Reporter: Wayne Steel
>Priority: Trivial
>
> 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 "-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)