[
https://issues.apache.org/jira/browse/NIFI-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247038#comment-16247038
]
ASF GitHub Bot commented on NIFI-4595:
--------------------------------------
GitHub user ijokarumawak opened a pull request:
https://github.com/apache/nifi/pull/2264
NIFI-4595: Add ConsumeAzureEventHub.
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [x] Is your initial contribution a single, squashed commit?
### For code changes:
- [x] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [x] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijokarumawak/nifi nifi-4595
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2264.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2264
----
commit f45d305b2db38e2a2ca6ebd1398dc79c7aee4398
Author: Koji Kawamura <ijokaruma...@apache.org>
Date: 2017-11-08T14:20:58Z
NIFI-4595: Add ConsumeAzureEventHub.
----
> 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)
