You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by zenfenan <gi...@git.apache.org> on 2018/06/13 17:34:41 UTC

[GitHub] nifi issue #2751: NIFI-5221: Added 'Object Tagging' functionalities to S3 Pr...

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?



---