[
https://issues.apache.org/jira/browse/NIFI-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105644#comment-15105644
]
Daniel Cave commented on NIFI-1096:
-----------------------------------
Are you thinking that you would aggregate properties for like processors to the
process group and then when redeploying the template for that process group it
would cascade all properties down to the processors?
How are you going to key same processors with different names (i.e. GetFile
"MyFile.txt" and GetFile "MyOtherFile.txt") Processor name be key?
Sounds very useful to me depending on how you apply the processor grouping and
property inheritance. Anything that makes the "code" more reusable is always
helpful, in my opinion.
> Add Process Group Configuration?
> --------------------------------
>
> Key: NIFI-1096
> URL: https://issues.apache.org/jira/browse/NIFI-1096
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Configuration, Core Framework
> Reporter: Ryan Leary
> Priority: Minor
> Fix For: 1.0.0
>
>
> This is as much a request for comments as feature request.
> I have a group of Processors that I often group into a Process Group. I make
> a template of these processors. From there, I want to reuse that Process
> Group several times, but with changing only a couple of configuration options
> within the underlying Processors.
> It would be really nice if we could a) have templated process groups, and b)
> add configuration options to a process group that processors within the group
> could reference.
> As a concrete example, if I have two processors that push to the same Kafka
> topic, I'd like to configure that at the "Process Group" level rather than
> having to enter the process group, and modify the configuration of two
> processors.
> Feedback appreciated! I'm a newbie to the NiFi codebase, but could look at
> what would be required to implement it if it's something people would find
> useful/would be merged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
