[
https://issues.apache.org/jira/browse/NIFI-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328629#comment-16328629
]
ASF GitHub Bot commented on NIFI-4777:
--------------------------------------
Github user adfel70 commented on the issue:
https://github.com/apache/nifi/pull/2405
@markap14,
The schema registry still has a cache in
[here](https://github.com/apache/nifi/blob/7c1ce172232d5fd8ab2a1c1649a9dcbf1a9d08d7/nifi-nar-bundles/nifi-confluent-platform-bundle/nifi-confluent-schema-registry-service/src/main/java/org/apache/nifi/confluent/schemaregistry/client/CachingSchemaRegistryClient.java#L28).
There were previously 2 caches, that was the reason i removed the ones in
the rest client.
> ConfluentSchemaRegistry Controller service fails to fetch schema if id not in
> cache and schema is not latest
> ------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-4777
> URL: https://issues.apache.org/jira/browse/NIFI-4777
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.5.0
> Reporter: AdFel
> Priority: Major
> Attachments: 0012-get-schema-by-id-even-if-not-latest.patch
>
>
> If the controller service was down and the schema was updated,
> the schema will not be found, even though it exists just because it is not
> the latest version.
> This fix searches for uncached schemas through the registry's subjects to
> figure out which version of the subject it was, even if it is not the latest
> schema.
> This patch is for version 1.5.0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
