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

Posted to issues@nifi.apache.org by "Juan C. Sequeiros (Jira)" <ji...@apache.org> on 2020/01/08 15:43:00 UTC

[jira] [Created] (NIFI-6993) FetchS3 does not prepend user defined S3 metadata keys with s3.

Juan C. Sequeiros created NIFI-6993:
---------------------------------------

             Summary: FetchS3 does not prepend user defined S3 metadata keys with s3.<s3 metadtata>
                 Key: NIFI-6993
                 URL: https://issues.apache.org/jira/browse/NIFI-6993
             Project: Apache NiFi
          Issue Type: New Feature
          Components: Extensions
    Affects Versions: 1.10.0
            Reporter: Juan C. Sequeiros
            Assignee: Juan C. Sequeiros


S3 allows the assignment of user defined metadata.

User defined metadata resides in its own "metadata" array and is called by the "getUserMetadata" function of the S3 java SDK [1]

When NIFI pulls the object and if there is user defined metadata it adds the metadata key / value as its literal key name.

This could lead to unintended NiFi attributes being replace like "filename"

A better approach is to prepend the S3 pulled metadata with s3 similar to how Fetchs3 prepends the other metadata of the object with s3.<metadata key>

[1] [https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/model/ObjectMetadata.html#getUserMetadata--]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)