nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James McMahon <jsmcmah...@gmail.com>
Subject Re: Process Groups and StandardClassificationService
Date Mon, 13 Mar 2017 12:04:05 GMT
Joe what is considered best practice for StandardClassificationService,
StandardHttpContextMap, and StandardSSLContextService in different process
groups? Should a new instance of each be created that is specific for each
and every process group? Or are common instances of one or more of these
services typically shared across process groups?

Regards,
Jim

On Mon, Mar 13, 2017 at 7:47 AM, Joe Skora <jskora@gmail.com> wrote:

> James,
>
> I believe that even with multi-tenant isolation the graph is managed as a
> whole so any change bumps the version for the whole thing.
>
> Regards,
> Joe
>
> On Mon, Mar 13, 2017 at 7:00 AM, James McMahon <jsmcmahon3@gmail.com>
> wrote:
>
>> Good morning. My co-worker and I have independent Process Groups, PGA and
>> PGB. Both exist at the workflow level immediately under NiFi Flow. Each
>> process group does indeed appear to have its own unique identifier. However
>> as we each run our workflows we find that we are periodically being told by
>> NiFi to refresh because the other has made updates. I noticed that we have
>> each defined instances of StandardClassificationService. Could that be the
>> reason we were getting these refresh messages?
>>
>> In general how should StandardClassificationService,
>> StandardHttpContextMap, and StandardSSLContextService be instantiated for
>> process groups? Should there only be one of each service and mapfor NiFi
>> Flow, shared by all process groups and processors under NiFi flow? Or
>> should each process group have its own instance, and - if so - why are we
>> experiencing these refresh messages that appear to be driven by changes in
>> the other independent process group?
>>
>> Thank you in advance for your help. -Jim
>>
>
>

Mime
View raw message