[
https://issues.apache.org/jira/browse/NIFI-4646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272703#comment-16272703
]
ASF subversion and git services commented on NIFI-4646:
-------------------------------------------------------
Commit 3df3ff6c610760c3adb1dffdd75d8cbaed1b471b in nifi's branch
refs/heads/master from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=3df3ff6 ]
NIFI-4646: This closes #2306.
- Ensuring the reason behind the SchemaNotFoundException is reported when
interacting with the configured SchemaRegistry.
Signed-off-by: joewitt <[email protected]>
> 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
> Fix For: 1.5.0
>
>
> 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)
