[
https://issues.apache.org/jira/browse/NIFI-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17381886#comment-17381886
]
Arsen Tavitov commented on NIFI-8785:
-------------------------------------
[~pvillard] we have already tested our issue on version 1.14.0 with applied
commit from:
[https://github.com/apache/nifi/commit/057b4af48249b8c22f4f914aac4c7ac4c3f5693c]
Unfortunately, we were able to reproduce the error that I have described above.
I have even contacted with Dmitry Ibragimov (who created NIFI-8296 issue). If I
have understood him correctly, they had more of performance issue with Nifi
rather than with schema retrieval.
> AvroReader controller can't get confluent schema IDs except only the latest
> ---------------------------------------------------------------------------
>
> Key: NIFI-8785
> URL: https://issues.apache.org/jira/browse/NIFI-8785
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.12.1
> Environment: CentOS7
> Reporter: Arsen Tavitov
> Priority: Major
> Attachments: nifi-app.rar
>
>
> While trying to read Confluent Schema Registry Avro files(from Kafka) with
> different schema IDs with AvroReader controller error "could not get Schema
> with id: <schema id>" appears.
> NiFi version: 1.12.1
> Confluent Schema Registry version: 5.5.2
> Using the following test flow in Nifi
> ConsumeKafka_2_6 1.12.1 ---> ConvertRecord 1.12.1
> In ConvertRecord processor we are using AvroReader controller as record
> reader.
> AvroReader controller properties:
> * schema access strategy: confluent content-encoded schema reference
> * schema registry: Confluent Schema Registry controller
> * schema name: ${schema.name} (default value)
> * schema version: no value set
> * schema branch: no value set
> * schema text: ${schema.text} (default value)
> * cash size: 1000 (default value)
> Similar issue:
> [https://community.cloudera.com/t5/Support-Questions/Nifi-ConsumeKafakRecord-0-11-Throws-Error-quot-Could-not/td-p/185636]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
