You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/01/04 19:15:01 UTC

[jira] [Commented] (NIFI-4595) Add ConsumeAzureEventHub processor

    [ https://issues.apache.org/jira/browse/NIFI-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311879#comment-16311879 ] 

ASF subversion and git services commented on NIFI-4595:
-------------------------------------------------------

Commit 98af3dc4cd56da324bb4572aab2dc395338ed45d in nifi's branch refs/heads/master from [~ijokarumawak]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=98af3dc ]

NIFI-4595: This closes #2264. Add ConsumeAzureEventHub.

Signed-off-by: joewitt <jo...@apache.org>


> Add ConsumeAzureEventHub processor
> ----------------------------------
>
>                 Key: NIFI-4595
>                 URL: https://issues.apache.org/jira/browse/NIFI-4595
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Koji Kawamura
>            Assignee: Koji Kawamura
>
> As reported by NIFI-2835, the existing GetAzureEventHub processor does not handle partition distribution among nodes in a NiFi cluster, and handling offset information across NiFi restart.
> The processor uses PartitionReceiver directly, however, there's another approach to receive events from Event Hub, that is using EventProcessorHost class.
> EventProcessorHost uses Azure Storage to store consumer group offset information so that it can distribute consumer load among consumer instances within the same group. Also this way can handle restart and NiFi cluster scale scenario better.
> In addition to above enhancements, we could also add Record data model capability to new ConsumeAzureEventHub. Similar to ConsumeKafkaRecord processor.



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