Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2020
will have to take more of a look. As a general practice to help reviewers
it is probably best during the review/feedback phase to just add new commits
rather than force commit on top of it. This helps to see/discuss progress
rather than starting over. No biggie just bringing it up to help you help your
reviewers.
At this stage I need an instance of Kudu to test against. Did some looking
into it last night and it looked like it was going to be a bit involved than I
had time for. So hopefully myself or someone else familiar with kudu can help
more soon. You've done some really nice work in here for sure.
As for other processors with similar patterns the gotcha can be whether
their clients auto reconnect, are thread safe, etc.. Each situation can differ
quite a lot.
Thanks
---
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.
---
