You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Brandon DeVries (JIRA)" <ji...@apache.org> on 2016/07/01 14:39:11 UTC
[jira] [Updated] (NIFI-2160) Enabled ControllerServices disabled on
restart
[ https://issues.apache.org/jira/browse/NIFI-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon DeVries updated NIFI-2160:
----------------------------------
Description:
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
was:
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
> 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)