PutAzureEventHub

Description:

Sends the contents of a FlowFile to Windows Azure Event Hubs. Note: the content of the FlowFile will be buffered into memory before being sent, so care should be taken to avoid sending FlowFiles to this Processor that exceed the amount of Java Heap Space available. Also please be aware that this processor creates a thread pool of 4 threads for Event Hub Client. They will be extra threads other than the concurrent tasks scheduled for this processor.

Tags:

microsoft, azure, cloud, eventhub, events, streams, streaming

Properties:

In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property is considered "sensitive", meaning that its value will be encrypted. Before entering a value in a sensitive property, ensure that the nifi.properties file has an entry for the property nifi.sensitive.props.key.

NameDefault ValueAllowable ValuesDescription
Event Hub NameThe name of the event hub to send to
Event Hub NamespaceThe namespace that the event hub is assigned to. This is generally equal to <Event Hubs Name>-ns
Shared Access Policy NameThe name of the shared access policy. This policy must have Send claims.
Shared Access Policy Primary KeyThe primary key of the shared access policy
Sensitive Property: true
Use Azure Managed Identityfalse
  • true
  • false
Choose whether or not to use the managed identity of Azure VM/VMSS
Partitioning Key Attribute NameIf specified, the value from argument named by this field will be used as a partitioning key to be used by event hub.
Maximum batch size100Maximum count of flow files being processed in one batch.

Relationships:

NameDescription
successAny FlowFile that is successfully sent to the event hubs will be transferred to this Relationship.
failureAny FlowFile that could not be sent to the event hub will be transferred to this Relationship.

Reads Attributes:

None specified.

Writes Attributes:

None specified.

State management:

This component does not store state.

Restricted:

This component is not restricted.

Input requirement:

This component requires an incoming relationship.

System Resource Considerations:

ResourceDescription
MEMORYAn instance of this component can cause high usage of this system resource. Multiple instances or high concurrency settings may result a degradation of performance.