[
https://issues.apache.org/jira/browse/NIFI-14289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928923#comment-17928923
]
Chris Sampson commented on NIFI-14289:
--------------------------------------
NIFI-14288 could be combined with the existing FetchS3Object and
GetS3ObjectMetadata processors in order to achieve the same outcome
The additional flexibility with such a setup would be beneficial for use cases
where the object content only needs to be retrieved based upon examination of
tags and/or metadata, e.g. if a specific tag/value exists, then disks the
object as flowfile content
The FetchS3Object update would be more useful when chained more directly with
ListS3, or other processors, when it is known that all objects, tags &
metadata will always be wanted within the nifi flow
> FetchS3Object should optionally allow retrieval of all metadata and tags
> ------------------------------------------------------------------------
>
> Key: NIFI-14289
> URL: https://issues.apache.org/jira/browse/NIFI-14289
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 2.2.0
> Reporter: Chris Sampson
> Priority: Major
>
> The FetchS3Object processor currently retrieve the object's metadata, but
> only returns a subset as attributes (e.g. the ETag is returned as s3.etag).
> Options should be added to the processor in order to allow:
> * all metadata to be returned as flowfile attributes (where not always used
> as defined attributes)
> * all tags to be returned as flowfile attributes (as this requires additional
> IAM access, the tags should only be retrieved if their retrieval is enabled
> via processor properties)
> The retrieval of metadata and tags should respect the requested versionId of
> the Object being fetched (when provided, otherwise retrieve the latest).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
