You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/01/08 03:15:00 UTC

[jira] [Commented] (NIFI-5920) Processor to tag an existing S3 object

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

ASF subversion and git services commented on NIFI-5920:
-------------------------------------------------------

Commit a8e59e52af5144c6238230bd792d01ca6daafadf in nifi's branch refs/heads/master from Stephen Goodman
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a8e59e5 ]

NIFI-5920: Tagging an object in S3

Unit tests and functionality for tagging an object in S3.

Set FlowFile attributes directly from tags retrieved from S3.

Add guard clauses to ensure evaluated properties are not blank.

This closes #3239.

Signed-off-by: Koji Kawamura <ij...@apache.org>


> Processor to tag an existing S3 object
> --------------------------------------
>
>                 Key: NIFI-5920
>                 URL: https://issues.apache.org/jira/browse/NIFI-5920
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.9.0
>            Reporter: Stephen Goodman
>            Priority: Minor
>             Fix For: 1.9.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> A common use case for data aggregation projects is to use AWS S3 as data staging zone. Files are uploaded to S3 buckets from various sources, and NiFi is used to fetch the S3 objects and perform additional processing.
> AWS S3 lifecycle management policies allow transitioning S3 objects from standard storage to glacier storage for cost savings in long-term storage. A lifecycle management rule can be set to transition an object that has a particular tag. 
> Currently, the only way to tag an S3 object via NiFi is to through the PutS3Object processor. For the above use case, where an S3 object was uploaded by a second- or third-party, it would be very helpful to have a TagS3Processor that can tag an existing S3 object, so that the s3 lifecycle management policy can be triggered after NiFi has processed the S3 object.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)