You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Bryan Bende (JIRA)" <ji...@apache.org> on 2019/03/27 20:31:00 UTC
[jira] [Updated] (NIFI-5856) Add capability to assign available
matching controller services to processors during import from registry
[ https://issues.apache.org/jira/browse/NIFI-5856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Bende updated NIFI-5856:
------------------------------
Labels: SDLC (was: )
> Add capability to assign available matching controller services to processors during import from registry
> ---------------------------------------------------------------------------------------------------------
>
> Key: NIFI-5856
> URL: https://issues.apache.org/jira/browse/NIFI-5856
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.8.0
> Reporter: Ed Berezitsky
> Priority: Major
> Labels: SDLC
>
> As a user I would like to reduce manual configuration of components after importing flows from NIFI registry.
> Use cases:
> * a component uses controller service(s) defined in a scope of *parent* (or higher) level (e.g. record-based processors, DB pools, etc) can have controllers assigned by default, if ID registered is not available (versioned from another NIFI instance)
> * a controller service that is in a scope of imported flow uses another controller in a scope of *parent* (or higher) level (e.g. Record readers/writer using schema registry).
> Current state:
> * a lookup for a controller service is done by ID. If ID is not found, a controller won't be assigned and property of a processor/controller will stay blank and will require manual configuration/selection
> Specifications/Requirements:
> * Change current behavior to enable default assignment of controller services to processor/controller property in case desired controller service cannot be found by ID.
> * in order to reduce wrong automatic assignments, both type and name of a controller service should be considered.
> * Since names aren't unique, have a NIFI property to specify strict and nonstrict policy for multi-match:
> ** strict mode will restrict automatic assignment of controller service, and property in the processor/controller will stay blank (as per current specification).
> ** nonstrict mode will allow any of matching controllers to be assigned (first found).
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)