[
https://issues.apache.org/jira/browse/NIFI-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16645140#comment-16645140
]
Bryan Bende commented on NIFI-5674:
-----------------------------------
If you publish a new version of a process group, and then you had 10 instances
of it imported, currently you would have to go to each one upgrade each one
individually. I think we could offer ability to set a versioned process group
to auto-upgrade, but this is definitely something the user needs to opt in to
as in many cases it may be scary to have upgrades happening without realizing.
We could also offer better ways to bulk upgrade. In my opinion, investing
effort in improvements to versioned flows would make more sense than doing a
lot of work around templates.
> Add referenceable templates
> ---------------------------
>
> Key: NIFI-5674
> URL: https://issues.apache.org/jira/browse/NIFI-5674
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.5.0, 1.6.0, 1.7.0
> Reporter: Scott Wilburn
> Priority: Major
> Labels: class, templates
>
> Everyone knows how important code re-use is. NiFi's templates work great for
> this if you only have a handful of flows to use them in. Templates act more
> like copy-paste code re-use, because each time you apply a template, you are
> making a separate copy of the XML code and applying it to your canvas. What's
> missing is the ability to maintain one copy of the code, so that you can make
> changes to logic embedded in a template and have those changes applied to all
> instances of that code. It should work more like a library of classes in an
> OO language, or at least have that as an option. I propose having a type of
> template that can be applied in a read-only state, linked somehow to the
> saved template. If the source template is updated, changes to all instances
> of the template should be applied. I would imagine it would act similar to
> how variables are changed, where it has to stop all processors, apply the
> changes, then restart them. I think the same general idea could be applied to
> templates.
> Referenceable templates would make creating and maintaining large NiFi
> deployments much easier and less error prone. I know it's been talked about
> in the groups before, but I think it's time to put some action behind it now.
>
> Thanks,
> Scott
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
