Hi all, Is there a consensus on creating thread pools and managing them within processors (as opposed to using the Concurrent Tasks to handle thread management)?
In particular, we've rolled a different version of the GetKafka processor, but it doesn't use the getConcurrentTasks() like the current version does. Instead, we extend AbstractSessionFactoryProcessor, create our own thread pool in onTrigger, and handle shutdowns / restarts with the remaining lifecycle hooks. In any case, it's outside of the context of the concurrent tasks managed in NiFi. Goodness / badness? Thanks, -- Brian Ghigiarelli
