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

Joe Witt commented on NIFI-12709:
---------------------------------

Unpack content takes compressed data and turns it into uncompressed data (at 
least when the data is a zip for instance).  I don't think storing both 
attributes is useful because on the output side the concept of its compressed 
representation is largely gone (other than in provenance which we already 
capture).

As far as storing 'Last metadata change' and 'last access time' these seem like 
great candidates to start capturing from various processors like this one and 
others.  I think that requires a bit more thought/strategery on where to store 
common attributes of interest so that components can use/apply them in standard 
ways. 

> UnpackContent should save attributes from the zip entries as flowfile 
> attributes where possible
> -----------------------------------------------------------------------------------------------
>
>                 Key: NIFI-12709
>                 URL: https://issues.apache.org/jira/browse/NIFI-12709
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Joe Witt
>            Assignee: Daniel Stieglitz
>            Priority: Major
>
> In an email from Jan 31st to users list titled 'ExecuteStreamCommand failing 
> to unzip incoming flowfiles'
> Issue is that UnpackContent doesn't capture much useful metadata.  The user 
> wants last modified date which is easily available, but also creator, 
> creation time, and owner which are less obviously avaialble at least not 
> consistently.  But there is a concept of extra fields we can extract metadata 
> from.  We have those same fields available from Tar files so it is natural 
> users would also want these.  Given their names aren't standard though I see 
> why Tar is the only one we currently say we support pulling those for.  If we 
> at least captured the metadata then flow builders can use it in their flows 
> as they wish whereas right now we dont expose that information.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to