nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (NIFI-5856) Add capability to assign available matching controller services to processors during import from registry
Date Mon, 29 Jul 2019 14:30:00 GMT


ASF subversion and git services commented on NIFI-5856:

Commit f8e93186f53917b1fddbc2ae3de26b65a99b9246 in nifi's branch refs/heads/master from Mark
[;h=f8e9318 ]

NIFI-5856: When exporting a flow that references a Controller Service, also include the ExternalControllerServiceReference's
in the snapshot. When importing/updating a flow, if a Controller Service that is inherited
is referenced, attempt to find any one ControllerService that gets inherited whose name matches
the reference and if found link to that Controller Service.

NIFI-5856: Fixed checkstyle violation

NIFI-5856: Addressed review feedback

NIFI-5856: When assigning a matching Controller Service at a higher level for Process Group
import/update, ensure that we consider the User's read permissions when selecting the Controller

This closes #3553.

Signed-off-by: Bryan Bende <>

> Add capability to assign available matching controller services to processors during
import from registry
> ---------------------------------------------------------------------------------------------------------
>                 Key: NIFI-5856
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.8.0
>            Reporter: Ed Berezitsky
>            Assignee: Mark Payne
>            Priority: Major
>              Labels: SDLC
>             Fix For: 1.10.0
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
> 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

View raw message