[
https://issues.apache.org/jira/browse/NIFI-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034773#comment-17034773
]
ASF subversion and git services commented on NIFI-6873:
-------------------------------------------------------
Commit 62606ff89a5947197fc0a92adae9e7a5104ca2b7 in nifi's branch
refs/heads/master from Joe Ferner
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=62606ff ]
NIFI-6873: Added support for replacing a process group
- decoupled flow update request behavior from VersionsResource into new
abstract FlowUpdateResource
- added replace process group functionality in ProcessGroupResource
- parameterized FlowUpdateResource and created entity hierarchies to allow for
maximum code sharing across different update types
- refactored flow update methods to make use of commonality across different
update types whenever possible
- fixed issues in StandardProcessGroup verify update methods where same
components existed in different ancestry chains but were considered a match
when they shouldn't be
- improved StandardProcessGroup to properly match up components on update
using generated versioned component ids, when necessary to allow for update
flow to efficiently match common components on flow import
This closes #4023.
Signed-off-by: Mark Payne <[email protected]>
> Add support to import versioned flow
> ------------------------------------
>
> Key: NIFI-6873
> URL: https://issues.apache.org/jira/browse/NIFI-6873
> Project: Apache NiFi
> Issue Type: Task
> Components: Core Framework, Core UI
> Reporter: Matt Gilman
> Assignee: Joe Ferner
> Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When integrating with a NiFi Registry, NiFi can generate versioned flows to
> store in the registry. We should also allow these versioned flows to be
> imported directly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)