[
https://issues.apache.org/jira/browse/NIFI-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261160#comment-16261160
]
ASF subversion and git services commented on NIFI-4459:
-------------------------------------------------------
Commit 412b3fbbe2d43ad67e1e119586c507bd5258cccb in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=412b3fb ]
NIFI-4459: This closes #2240. Catch Exception if trying to iterate over many
confluent schemas and unable to load one; in this case log a WARNING and
continue on; also updated Jersey client to newest
Signed-off-by: joewitt <joew...@apache.org>
> Confluent Schema Registry - not tolerant to error in single Subject
> -------------------------------------------------------------------
>
> Key: NIFI-4459
> URL: https://issues.apache.org/jira/browse/NIFI-4459
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.4.0
> Reporter: Dave Torok
> Assignee: Mark Payne
> Priority: Minor
> Fix For: 1.5.0
>
>
> Getting Could not find Schema with id 12345 from the Confluent Schema
> Registry.
> Root cause:
> 1. RestSchemaRegistryClient.java - gets all subjects from the registry
> {noformat}https://{registry}/subjects{noformat}
> 2. Iterates through the subjects to get schema IDs (getSchema method line
> 113-126)
> {noformat}https://{registry}/subjects/{subjectname}/ids/latest{noformat}
> 3. If ANY subject in the list of subjects has an error / resource not
> found, lookup FAILS, even if the subject with the matching ID is anywhere in
> the list of subjects.
> Proposed Fix:
> Tolerate individual subject calls that return errors (NOT_FOUND status).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
