Github user mattyb149 commented on the pull request:
https://github.com/apache/nifi/pull/180#issuecomment-177632224
@rpmiskin That's a good idea for the ES ControllerService and
ReportingTask, I hadn't considered the ReportingTask so I didn't think there
would be enough need for the ControllerService. I think a breaking change would
be ok in the future if we have a migration path (moving the properties from the
processor to the controller service). I'd like to get these out for 0.5.0 so
the community can use them, then we can gather feedback and see if/when we want
to go the ControllerService route. What do you think?
Also I've updated this PR to incorporate your comment on logging, and added
more unit tests to exercise the non-happy-path processing.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
