[
https://issues.apache.org/jira/browse/NIFI-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327401#comment-16327401
]
ASF GitHub Bot commented on NIFI-4777:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2405
@adfel70 thanks for the contribution! I'm a bit concerned about the
ramifications of this change as-is, though. If I'm understanding the code
change, it appears to be removing all caching from the controller service. I
don't think that's what we want to do, as network problems or having the
Confluent Schema Registry go down would cause the dataflow to stop. I think if
we want to avoid the caching mechanism, then we would need to expose a property
to allow the user to choose whether or not they want to do so - or how long
they want to cache the schema.
> 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
> 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)
