Re: NiFi to S3

[Sivaprasanna]

Adrian,

Current version of S3 processors in Apache NiFi don’t have the object
tagging feature. I think it was recently added to the AWS S3 SDK owing to
the new GDPR regulation announced by EU. Please open a JIRA to have this
feature added to the S3 processors.

-
Sivaprasanna

On Thu, 12 Apr 2018 at 6:00 AM, Adrian D  wrote:

> Sir/Ma'am
>
> Is it possible to assign S3 object tags in NiFi upon writing? I am trying
> to implement object tagging as the PutS3Object processor is running. The
> closest reference to object tagging I found:
>
> https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html
>
> Please let me know. Thank you.
>

NiFi to S3

[Adrian D]

Sir/Ma'am

Is it possible to assign S3 object tags in NiFi upon writing? I am trying
to implement object tagging as the PutS3Object processor is running. The
closest reference to object tagging I found:

https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html

Please let me know. Thank you.

Suggestion: Apache NiFi component enhancement

[Sivaprasanna]

All,

Currently the "type" of a component is actually the component's canonical
class name which gets rendered in the UI as the class name with the
component version. This is good. However I'm thinking it is better to have
an annotation which a developer can use to override the component type.

How is it used?
I think an annotation can be sufficient. The framework checks if the
annotation is present or not, if it is present, it uses the name provided
there or else it uses the class name like how it is happening.

Why and where is it needed?

   - In scenarios where we devise a new naming convention and want to apply
   it to older components without breaking backward compatibility
   - A developer had created a component class with a name but later down
   the line, the developer or someone else wants to change it to something
   else, the reason could again be naming convention or just that the new name
   makes more sense
   - A component that has been built to work with third party tech, like
   Azure, MongoDB, S3, Druid processors but the later versions of that tech
   has been changed to something else by the original creators. (Something
   similar has happened to Azure's DocumentDB which got later rebranded as
   Azure CosmosDB). In such cases, without deprecating or rebuilding a new
   processor, this can be used.

Before creating a JIRA, I wanted to get the community's thoughts. Feel free
to share your thoughts, concerns. If everything seems fine, I'll start
working on the implementation.

-

Sivaprasanna