[
https://issues.apache.org/jira/browse/NIFI-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Torok updated NIFI-4459:
-----------------------------
Affects Version/s: (was: 1.5.0)
(was: 1.3.0)
1.4.0
Description:
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).
was:
NOTE: could not select "1.4.0" when creating this Jira.
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).
> 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
> Priority: Minor
>
> 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)
