[jira] [Updated] (NIFI-4746) ConfluentSchemaRegistry Controller service only uses latest schema, failing if schema changed

["AdFel (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

AdFel updated NIFI-4746:
------------------------
    Labels: confluent-kafka confluentic schema  (was: )
    Status: Patch Available  (was: Open)

This patch includes the changes to get schema by ID,
allowing nifi to read a record even if the latest schema was changed.

> ConfluentSchemaRegistry Controller service only uses latest schema, failing if schema changed
> ---------------------------------------------------------------------------------------------
>
>                 Key: NIFI-4746
>                 URL: https://issues.apache.org/jira/browse/NIFI-4746
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.4.0
>            Reporter: AdFel
>              Labels: confluent-kafka, confluentic, schema
>
> When ConsumeKafkaRecord_01X uses the ConfluentSchemaRegistry 1.4.0 the id in the magic byte is not used to merge the latest schema with the writer schema, as stated in the Apache Avro documentation. Nifi instead compares the id to the latest schema's ID, and if they do not match, the flowfile is sent to the parse.failure. To fix this bug the ConfluentSchemaRegistry controller should merge the writer's schema with the latest schema, using the ID written in the magic byte



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)