You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Bryan Bende (JIRA)" <ji...@apache.org> on 2019/03/21 18:53:00 UTC
[jira] [Commented] (NIFI-6135) DistributedMapCacheServer not
included in templates
[ https://issues.apache.org/jira/browse/NIFI-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798340#comment-16798340 ]
Bryan Bende commented on NIFI-6135:
-----------------------------------
I think this is the same issue described here - https://issues.apache.org/jira/browse/NIFI-2895
It is not specific to the DMC server, it is a general scenario where any CS that is not referenced through a chain that leads back to a processor on the canvas will not be included.
Since the DMC server is used through a network connection from the DMC client, there is no direct linkage to the DMC server.
We should just include all services that are part of the process groups selected in the template.
> DistributedMapCacheServer not included in templates
> ---------------------------------------------------
>
> Key: NIFI-6135
> URL: https://issues.apache.org/jira/browse/NIFI-6135
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.8.0
> Environment: Windows and Linux
> Reporter: Ed R
> Priority: Major
>
> When saving a template from a flow that includes DistributedMapCacheServer instances, those instances are not included in the template. (Or, at least, are not imported back when uploading the template.) The client instances are, but the server instances must be re-created from scratch every time.
>
> Steps to reproduce:
> Create a new process group
> Right-click Configure and add a DistributedMapCacheServer instance
> Create a template from the group
> Save the template to disk
> Delete the group and the template
> Import the template from disk
> Create a new group from that template
> Right-click Configure and see there is no longer a DistributedMapCacheServer instance
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)