[
https://issues.apache.org/jira/browse/NIFI-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359081#comment-15359081
]
Brandon DeVries commented on NIFI-2160:
---------------------------------------
My statements which you refer to in your first paragraph were simply for
background (to preempt the question "if they aren't being referenced, why does
it matter that they're disabled?"). If you want to argue that "it would be the
responsibility of your custom DSL to enable the CS if it is disabled", that is
a conversation that can be had. However, a feature that was available no
longer is, thus breaking backwards compatibility on a non-major release. This
is a (critical) problem.
As to your second paragraph... yes, the bug is that a "CS (regardless of it's
relationship to anything) was in ENABLED state when NiFi was shut down and is
DISABLED upon restart of NiFi". That could be the entire description of the
ticket... the rest is just context. If you're going to take on the ticket,
that's fantastic (and appreciated). Thanks.
> Enabled ControllerServices disabled on restart
> ----------------------------------------------
>
> Key: NIFI-2160
> URL: https://issues.apache.org/jira/browse/NIFI-2160
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Brandon DeVries
> Priority: Critical
> Fix For: 0.7.0
>
>
> As a result of the fix for NIFI-2032, *previously enabled ControllerServices
> become disabled after a restart* if they are not referenced by another
> component. However, we use a custom domain specific langauge that can
> reference a controller service from a query defined as a custom processor's
> property. This means that we use a number of controller service that are
> only used in this way (i.e. are never directly referred to by another
> component). Upon restart, these are now disabled causing issues with our
> flows.
> I have not yet stepped through the new enableControllerServices() \[1\]
> method to figure out exactly where the issue is coming from, but I wanted to
> get the ticket out there and on the radar, as this breaks backwards
> compatibility on a feature we heavily rely on.
> \[1\]
> https://github.com/apache/nifi/blob/0.x/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/service/StandardControllerServiceProvider.java#L301-336
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
