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

Adding Dynamic HTTP Headers to Confluent Schema Registry Requests

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.15.0
    • Fix Version/s: 1.15.0
    • Component/s: Extensions
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              katchison Knowles Atchison Jr
              Reporter:
              katchison Knowles Atchison Jr

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

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

                  Issue deployment