[
https://issues.apache.org/jira/browse/NIFI-14086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010830#comment-18010830
]
Greg Solovyev commented on NIFI-14086:
--------------------------------------
Yes. In my case, I can have multiple process groups that have the same name in
Nifi Registry, but need to have different names when deployed. When I am
importing a process group from Nifi Registry, it gets deployed with whatever
name it has in the registry. Here's a specific example. I have a process group
named "WEF Connector" which reads Windows logs from a Windows Event Collector
machine, gzips them, and uploads them to S3. I often deploy several WEF
Connectors on the same docker node in order to read events from multiple WEC
machines. I keep details of machine IP and access in parameter contexts, so in
this case I create a parameter context for each target WEC machine and assign
each parameter context to each copy of the "WEF Connector" process group. So,
to summarize, I have one process group in Nifi Registry called "WEF Connector".
This process group implements the feature of reading logs from a given windows
machine. I deploy two or three copies of WEF Connector to the same docker node
and assign separate parameter contexts to each copy of WEF Connector.
> Nifi toolkit pg-import command should allow specifying PG name
> --------------------------------------------------------------
>
> Key: NIFI-14086
> URL: https://issues.apache.org/jira/browse/NIFI-14086
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
> Reporter: Greg Solovyev
> Assignee: Greg Solovyev
> Priority: Minor
>
> Process groups templates in registry include name property, which translates
> into process group name when importing a process group from a registry. This
> makes it hard to have multiple instances of the same PG template within the
> same NiFi instance. The example that I am dealing with is that a PG template
> represents an implementation of a specific data connector (e.g., a connector
> that reads events from a Windows Event Collection server or a Syslog server,
> etc) and I need to deploy multiple copies of this connector to a single NiFi
> instance where each copy reads from a separate server. I cannot do this
> without accessing renaming process groups via NiFi UI or REST API, because
> # once a single copy is deployed from the registry, all other copies will
> fail to deploy due to name conflict.
> # NiFi toolkit does not support renaming a process group
> I have an implementation of this feature already in Anetac's NiFi fork
> [https://github.com/apache/nifi/commit/a6d36a721e19aa44ff77514809b1ca001211848e,]
> so this is just a matter of porting the change to main branch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
