You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Brandon DeVries (JIRA)" <ji...@apache.org> on 2016/12/09 14:03:58 UTC
[jira] [Created] (NIFI-3177) (Optionally?) Don't duplicate
controller servivces on template instantiation
Brandon DeVries created NIFI-3177:
-------------------------------------
Summary: (Optionally?) Don't duplicate controller servivces on template instantiation
Key: NIFI-3177
URL: https://issues.apache.org/jira/browse/NIFI-3177
Project: Apache NiFi
Issue Type: Improvement
Reporter: Brandon DeVries
Priority: Minor
When placing a template onto the graph, all included / required controller services are also created... even if an exact duplicate already exists (possibly even from a previous instance of the same template). It is definitely possible you might not want to reuse an existing controller service, so that shouldn't be the default behavior. However, it is also very likely that you *do* want to reuse a controller service.
Could we add a check on template instantiation that checks for controller service matches (name & configuration), and prompt with the option to either create new or use existing?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)