You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Knowles Atchison Jr (Jira)" <ji...@apache.org> on 2021/07/22 00:17:00 UTC
[jira] [Assigned] (NIFI-8936) Adding Dynamic HTTP Headers to
Confluent Schema Registry Requests
[ https://issues.apache.org/jira/browse/NIFI-8936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knowles Atchison Jr reassigned NIFI-8936:
-----------------------------------------
Assignee: Knowles Atchison Jr
> Adding Dynamic HTTP Headers to Confluent Schema Registry Requests
> -----------------------------------------------------------------
>
> Key: NIFI-8936
> URL: https://issues.apache.org/jira/browse/NIFI-8936
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 1.15.0
> Reporter: Knowles Atchison Jr
> Assignee: Knowles Atchison Jr
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The nifi confluent schema registry service does not currently expose any way to add arbitrary HTTP headers to requests going to the Confluent Schema Registry.
> When using Kafka Client infrastructure outside of NiFi when interacting with the Confluent Schema Registry, the Deserializer is set to be KafkaAvroDeserialzer.class. This class contains the SchemaRegistryClient from Confluent.
> One feature this client supports is the sending of HTTP Headers to the schema registry through properties on the client prefixed with "request.header.". This can be found in AbstractKafkaSchemaSerDeConfig (in Confluent's schema registry source code).
> I propose to add this functionality to the ConfluentSchemaRegistry.
> The controller will be updated to take in dynamic properties which will be validated as 'request.header.*'. These values will then be added to the requests going out via Jersey if present.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)