[
https://issues.apache.org/jira/browse/NIFI-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906002#comment-15906002
]
ASF subversion and git services commented on NIFI-3575:
-------------------------------------------------------
Commit 977aa6919cd97dacb1214c631f7055646e109472 in nifi's branch
refs/heads/master from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=977aa69 ]
NIFI-3575:
- Verify that when moving a snippet, we do not attempt to move a process group
into itself.
- Update the UI to ensure a subsequent move event cannot be triggered while a
previous move event is still in progress.
This closes #1582.
Signed-off-by: Andy LoPresto <[email protected]>
> Can lose entire process group when moving components into it from parent PG
> ---------------------------------------------------------------------------
>
> Key: NIFI-3575
> URL: https://issues.apache.org/jira/browse/NIFI-3575
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Joseph Percivall
> Assignee: Matt Gilman
> Priority: Critical
> Fix For: 1.2.0
>
>
> When you move any component from the parent group and drag and drop it into a
> process group, if you immediately enter the process group (within
> approximately half a second) the process group will cease to exist (even if
> it had contents already).
> If the UI renders the graph initially, attempting to refreshing the canvas
> returns "Unable to locate group with id: <id of process group that died>".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)