Github user simonellistonball commented on the pull request:
https://github.com/apache/nifi/pull/399#issuecomment-217411669
This needs a little bit more work. The goal here is to use a common pattern
from standard processors, however, while tests work fine, loading into NiFi
causes a duplicate of the standard processor nar and therefore unpredicatable
ordering. One solution to this would be to factor the base
AbstractListProcessor classes out of standard processors into processor-utils.
However, they have a legacy dependency on the distributed cache service which
would cause a circular dependency for this refactoring.
Short term solution would be to reimplement the trigger and state logic
direct in the Azure processors, which violates DRY.
Longer term it would be great to have clean Abstracts for some of these
common custom patterns in processor-utils, but that's for another issue and
another PR.
In the meantime I'll re-implement and update the PR, so please don't worry
about reviews right now.
---
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.
---
