[
https://issues.apache.org/jira/browse/NIFI-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511460#comment-16511460
]
ASF GitHub Bot commented on NIFI-5221:
--------------------------------------
Github user zenfenan commented on the issue:
https://github.com/apache/nifi/pull/2751
Actually after giving it some serious thought, the attribute approach does
make more sense. Easy from the flow development perspective, and even when
using ExecuteScript or a custom processor to parse and process content to
create appropriate tags, the developer can still add them to FlowFile
attributes.
So I’ll update this one to scrap the JSON approach and instead take a comma
separated list of tag prefixes which will be taken and scanned against the
incoming FlowFiles’ attributes to generate the tags. Makes sense?
> Add Object Tagging support for AWS S3 Processors
> ------------------------------------------------
>
> Key: NIFI-5221
> URL: https://issues.apache.org/jira/browse/NIFI-5221
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Sivaprasanna Sethuraman
> Assignee: Sivaprasanna Sethuraman
> Priority: Major
>
> AWS has introduced new set of functionalities that enable the S3 bucket and
> objects to be tagged. This can be useful for data classification purposes and
> with new regulatory process related to data are being introduced such as
> GDPR, object tagging can be quite useful and helpful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
