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 2022/01/04 16:41:00 UTC

[jira] [Commented] (NIFI-7371) Improve error handling of S3 processors

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

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

Commit 0d49371c53e1a6da80fdb33ecfbad13eb5b8cad1 in nifi's branch refs/heads/NIFI-9428 from Paul Grey
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0d49371 ]

NIFI-7371 Added FlowFile attributes for exceptions in S3 processors

This closes #5606

Signed-off-by: David Handermann <ex...@apache.org>


> Improve error handling of S3 processors
> ---------------------------------------
>
>                 Key: NIFI-7371
>                 URL: https://issues.apache.org/jira/browse/NIFI-7371
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.11.4
>            Reporter: endzeit
>            Assignee: Paul Grey
>            Priority: Major
>             Fix For: 1.16.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Currently the S3 processors, such as FetchS3Object, only expose the relationsships "success" and "failure". However the are a multitute of reasons why an interaction with an S3 storage might fail.
> As of now there is no easy way of knowing why a flow file was directed to the "failure" relationsship just by the flow file itself.
> A way of finding out the reason might be to search for a corresponing log / bulletin entry.
>  This seems rather complicated.
> A use case where having this information is useful could be when deciding whether
>  * the action should be retried, e.g. on a timeout,
>  * or the failure be handled, e.g. when the object for the specified key does not exists.
> I haven't looked much into the underlying AWS library yet as I wanted to discuss whether such an improvement is desired at all first?
>  If so, should the information be exposed via
>  * additional / other relationsships, such as in the FetchSFTP processor,
>  * or rather an attribute added to the flow file, such as in the ValidateXml processor?
> This might also apply to other AWS processors but we just have come across the S3 processors as we use them quite regulary.
> Any thoughts or comments would be highly appreciated!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)