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 GitHub Bot (JIRA)" <ji...@apache.org> on 2017/11/29 15:53:00 UTC

[jira] [Commented] (NIFI-4646) AbstractRecordProcessor: Report reason for SchemaNotFoundException

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

ASF GitHub Bot commented on NIFI-4646:
--------------------------------------

GitHub user mcgilman opened a pull request:

    https://github.com/apache/nifi/pull/2306

    NIFI-4646: AbstractRecordProcessor: Report reason for SchemaNotFoundException

    NIFI-4646:
    - Ensuring the reason behind the SchemaNotFoundException is reported when interacting with the configured SchemaRegistry.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mcgilman/nifi NIFI-4646

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/2306.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2306
    
----
commit f2e39b378befdd9440705602373e1a53df0867bb
Author: Matt Gilman <ma...@gmail.com>
Date:   2017-11-29T15:51:29Z

    NIFI-4646:
    - Ensuring the reason behind the SchemaNotFoundException is reported when interacting with the configured SchemaRegistry.

----


> AbstractRecordProcessor: Report reason for SchemaNotFoundException
> ------------------------------------------------------------------
>
>                 Key: NIFI-4646
>                 URL: https://issues.apache.org/jira/browse/NIFI-4646
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Matt Gilman
>            Assignee: Matt Gilman
>            Priority: Trivial
>
> When a schema registry is unable to retrieve a schema, the reason is reported in the corresponding exception. However, when that exception is handled in the corresponding record processor, the reasoning is not included in the ProcessException that is thrown for the framework to catch.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)