[NIFI-4459] Confluent Schema Registry - not tolerant to error in single Subject

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.5.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Dave Torok
• Created: 03/Oct/17 19:24
• Updated: 21/Nov/17 17:55
• Resolved: 21/Nov/17 17:55

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

https://{registry}/subjects

2. Iterates through the subjects to get schema IDs (getSchema method line 113-126)

https://{registry}/subjects/{subjectname}/ids/latest

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).

Issue Links

• links to: GitHub Pull Request #2240