nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Payne <>
Subject Re: Any down sides to putting a controller service in the same package as a processor?
Date Tue, 25 Sep 2018 19:35:19 GMT

The Mongo Controller Service already exists though, right? You cannot move it into the Processors
after it's already been released. That would change the 'bundle coordinates' for the controller
service and
would mean that any flow that uses it is no longer valid and would have to be reconfigured.


> On Sep 25, 2018, at 3:09 PM, Mike Thomsen <> wrote:
> Thanks. That's what I thought. I may also do that for the Mongo package
> because it should cut some space by not duplicating the Mongo driver.
> On Tue, Sep 25, 2018 at 2:46 PM Bryan Bende <> wrote:
>> That is fine for the CS implementation, the CS API should be in it's own
>> NAR.
>> On Tue, Sep 25, 2018 at 2:14 PM Mike Thomsen <>
>> wrote:
>>> I picked up NIFI-5224, which is for creating a Solr client service, and
>> was
>>> wondering if there are any gotchas or down sides to putting the
>> controller
>>> service in the same NAR as the processors that will use it. Is there any
>>> reason I would want to avoid that?
>>> Thanks,
>>> Mike

View raw message