[
https://issues.apache.org/jira/browse/NIFI-6315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854166#comment-16854166
]
ASF subversion and git services commented on NIFI-6315:
-------------------------------------------------------
Commit e7f4af68014ea99f1e351436d6a078ad4b3346a6 in nifi's branch
refs/heads/master from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e7f4af6 ]
NIFI-6315 Ensuring remote ports get tracked correctly when saving/retrieving
versioned flows
NIFI-6315 Renaming public ports during import/change-version when name alreadye
exists, and ignorning name change from flow diffs
NIFI-6315 Ensuring public ports get renamed during copy/paste
NIFI-6315 Set max concurrent tasks on Port based on value from VersionedPort
This closes #3488.
Signed-off-by: Koji Kawamura <[email protected]>
> Track remote input/output ports at any level when creating versioned flows
> --------------------------------------------------------------------------
>
> Key: NIFI-6315
> URL: https://issues.apache.org/jira/browse/NIFI-6315
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> NIFI-2933 added the ability to create remote input/output ports at any level.
> This information needs to be tracked when creating versioned flows that are
> saved to registry, otherwise it will be lost on import.
> The registry 0.4.0 release added a boolean to VersionedPort for this purpose:
> [https://github.com/apache/nifi-registry/blob/master/nifi-registry-core/nifi-registry-data-model/src/main/java/org/apache/nifi/registry/flow/VersionedPort.java#L26]
> NiFi's master branch needs to be updated to the 0.4.0 client which is part of
> NIFI-6311:
> [https://github.com/apache/nifi/pull/3485]
> CC: [~ijokarumawak] [~markap14]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
