[
https://issues.apache.org/jira/browse/NIFI-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-10300.
-------------------------------------
Fix Version/s: 1.18.0
Resolution: Fixed
> Add AzureEventHubRecordSink
> ---------------------------
>
> Key: NIFI-10300
> URL: https://issues.apache.org/jira/browse/NIFI-10300
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: David Handermann
> Assignee: Nathan Lee
> Priority: Major
> Fix For: 1.18.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> A new Record Sink Service should be implemented supporting transmission of
> record-oriented events to [Azure Event
> Hubs|https://azure.microsoft.com/en-us/services/event-hubs/].
> The current {{PutAzureEventHub}} Processor does not provide direct support
> for record-oriented FlowFiles. Implementing an {{AzureEventHubRecordSink}}
> would support sending record-oriented events using the {{PutRecord}}
> Processor, providing configurable input and output record formatting using
> standard services.
> The Azure Event Hub Record Sink should be implemented using the newer [Azure
> Event Hubs client
> library|https://docs.microsoft.com/en-us/java/api/overview/azure/messaging-eventhubs-readme?view=azure-java-stable].
> Similar to {{PutAzureEventHub}}, the Record Sink should support configurable
> authentication strategies, with initial support for Named Keys or [Default
> Azure
> Credentials|https://docs.microsoft.com/en-us/azure/developer/java/sdk/identity-azure-hosted-auth#default-azure-credential],
> which enables access using environment variables or Managed Identities.
> The Azure Event Hub Record Sink should be capable of sending one record per
> event, providing the option to implement other record batching strategies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
