[
https://issues.apache.org/jira/browse/NIFI-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846190#comment-16846190
]
ASF subversion and git services commented on NIFI-2933:
-------------------------------------------------------
Commit 8a50cb10b20bfdbf61fa1a769b817c86eab9653a in nifi's branch
refs/heads/master from Koji Kawamura
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8a50cb1 ]
NIFI-2933 Remote input/output ports at any PG
Specify remote access at port creation.
Incorporated comments, and finished refactoring.
Renamed RootGroupPort to PublicPort.
Fix error message for creating a connection from a child PG having only
PublicPorts.
Enhanced ProcessGroup instances rendered in the parent ProcessGroup
Loosen Port move check, allow moving public port between PG.
Show 'Remote NiFi Instance' info on Connection dialogs
Make labels narrative.
'Within Remote Group'.
Fixed DTO (de)serialization.
Return null only if all values are null.
This closes #3351.
Signed-off-by: Mark Payne <[email protected]>
> Remote input/output ports and local process groups should be treated as
> completely different components
> -------------------------------------------------------------------------------------------------------
>
> Key: NIFI-2933
> URL: https://issues.apache.org/jira/browse/NIFI-2933
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Matthew Clarke
> Assignee: Koji Kawamura
> Priority: Major
> Time Spent: 9.5h
> Remaining Estimate: 0h
>
> With the addition of Multi-tenancy users can restrict users to particular
> process groups. What these users cannot do is create input and output ports
> on the root canvas. Users should be able to create remote input/output ports
> within process groups and assign S2S policies to them. The only thing they
> should need an admin to do is add Servers as users and add the global
> "retrieve site-to-site details" policy. This allows for a better separation
> between dataflow designer/implementor/DFM and NiFi Admin. The added benefit
> of treating remote and local input/output ports as unique components is that
> you could add them anywhere in your flow including imbedded within process
> groups.
> Perhaps making them configurable as local or remote ports (defaulting to
> remote when added to root canvas and local when added within process group).
> This way we preserve backwards compatibility while still improving their
> usability in a multi-tenancy environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
