[
https://issues.apache.org/jira/browse/NIFI-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404855#comment-16404855
]
ASF GitHub Bot commented on NIFI-4777:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2405
Hey @adfel70 I think I was looking at this PR the wrong way. I didn't
notice the addition of the POST request, which is very vital. Because of that,
I thought this was making a very large number of requests, but after reviewing
the confluent API docs and reviewing the code again it all makes sense. The
caching in this layer is different than the caching at the higher layer but was
only really necessary for the routine that was there previously, before the
POST request. I think your solution handles this case much better than the
previous solution. And more importantly your solution appears to be correct :)
I was able to test locally and see that if i changed the schema reference to an
older version of an existing schema that things work correctly with this PR and
did not without the PR. So I've merged this to master. Thanks for the fix and
for the patience in getting it all sorted out!
> 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
> Fix For: 1.6.0
>
> 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)
