Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-8785

AvroReader controller can't get confluent schema IDs except only the latest

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.12.1
    • Fix Version/s: 1.15.0
    • Component/s: Extensions
    • Labels:
      None
    • Environment:
      CentOS7
    • Flags:
      Important

      Description

      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 

        Attachments

        1. Kafka_Confluent_Schema_Suffering.json
          31 kB
          Arsen Tavitov
        2. nifi-app.rar
          960 kB
          Arsen Tavitov

          Issue Links

            Activity

              People

              • Assignee:
                pvillard Pierre Villard
                Reporter:
                atavitov Arsen Tavitov
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 50m
                  50m