Github user josephxsxn commented on the issue:
https://github.com/apache/nifi/pull/1800
1) I'll look into taking the inner classes out but will need to look at how
the permissions scopes are working between them first.
2) Will look into applying the KeeperException recommendation to clean the
code up some.
3) Will fix versions
4) I agree, I got tired of fighting maven's arch type generator. Will
repackage things to facilitate a generic election API like the jira kinda talks
about.
5) Plan is to make the GetEventHubProcessor use this as it has some major
issues in clustered deployments with duplication of data. Unlike Kafka which
uses a consumer group to only allow 1 reader per partition. In EventHub your
allowed 5 readers per partition, so we need a method to discover alive workers,
elect the leader, have the leader assign partition work into the shared cache,
and then run.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
