It should be hierarchical. The Set of Controller Services to match by name is
obtained by calling `parentGroup.getControllerServices(true)` where parentGroup
is the Process Group that components are to be added to.
@Eric, the code that does the matching can be found at [1].
Thanks
Mark
[1]
Do you have any controller services in process groups above the “controller
container”?
I can’t remember if it is based on only the immediate parent, or the entire
hierarchy.
On Sat, May 23, 2020 at 8:00 PM Andrew Grande wrote:
> Maybe something is going on with specific types or hierarchies.
Maybe something is going on with specific types or hierarchies. I've
noticed DefaultSslContext didn't get assigned, even though it was the only
one available. Does autowiring logic apply to this one?
Andrew
On Sat, May 23, 2020, 3:54 PM Eric Secules wrote:
> Hi Bryan,
>
> I have noticed this
Hi Bryan,
I have noticed this behaviour sometimes, but not all the time I am running
the latest registry and NiFi versions. I haven't found a conclusive pattern
but I have a hunch that it has to do with having versioned process groups
within versioned process groups. My deployment strategy is
Yes, I should have clarified this. Thanks Bryan. This is the solution for the
generic use case. The original question was about reducing the controller to
only a single instance of a specific controller service implementation, which
is how the tangent got started.
Andy LoPresto
If you use registry >= 0.5.0 And nifi >= 1.10.0, then it will auto select
external controller services with the same name as long as there is only
one of the same type with same name (name is not unique).
On Sat, May 23, 2020 at 3:34 PM Andy LoPresto wrote:
> My position is that we don’t claim
My position is that we don’t claim completely automated deployment as a
feature, so manually setting the controller service IDs is not exposed.
Technically, they are defined in the flow.xml.gz and could be modified by an
administrator to be static after generation. This would require frequent
Aren't those IDs generated? How can one enforce it?
Andrew
On Sat, May 23, 2020, 10:53 AM Andy LoPresto wrote:
> If you want the process to be completely automated, you would have to
> enforce the controller service IDs to be identical across environments.
> Otherwise deployment would need a
If you want the process to be completely automated, you would have to enforce
the controller service IDs to be identical across environments. Otherwise
deployment would need a manual intervention to reference the specific
controller service in the proper component.
Andy LoPresto
Thank you Andy, certainly appreciate you looking at this. The use of a
frontend proxy is an excellent point, both to handle the routing as well as
adding isolation for Nifi.
Thanks again for the help.
patw
On Fri, May 22, 2020 at 3:53 PM Andy LoPresto wrote:
> Thanks Pat. The S2S protocol
10 matches
Mail list logo
