[ 
https://issues.apache.org/jira/browse/NIFI-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576033#comment-14576033
 ] 

ASF subversion and git services commented on NIFI-427:
------------------------------------------------------

Commit 5c1afc0897a939bcde803c07216be91b6c4d0c03 in incubator-nifi's branch 
refs/heads/develop from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=5c1afc0 ]

NIFI-427: Allow Process Groups to be deleted as long as no incoming or outgoing 
connections (unless they are also selected), all components stopped, no 
FlowFiles queued


> Too many steps to delete flows
> ------------------------------
>
>                 Key: NIFI-427
>                 URL: https://issues.apache.org/jira/browse/NIFI-427
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework, Core UI
>            Reporter: Ryan Blue
>            Assignee: Mark Payne
>             Fix For: 0.2.0
>
>         Attachments: 
> 0001-NIFI-427-Allow-Process-Groups-to-be-deleted-as-long-.patch
>
>
> I've been building some templates lately, but I'm running into some annoying 
> policy problems. I would like to build templates that include a processor 
> group and sample processors hooked up to its input and output ports. So the 
> template begins with getting data from a directory, but the user can easily 
> replace the GetFile processor with something else.
> The problem is when I try to delete processors brought in by the template. I 
> think this is a fairly common case: templates can be added easily and should 
> be deleted easily (e.g., oops, wrong template!). However, when I try to 
> highlight the template processors and delete, I get an error that says the 
> group is not empty. I go inside the group, select all. and delete, but that 
> fails because there are incoming connections. So I finally have to leave the 
> group and delete the non-group processors and connections, then enter the 
> group, delete everything, leave the group, and delete the empty group.
> This doesn't fit with my idea of easily bringing in tasks and easily removing 
> them. Am I doing something wrong?
> Can the processor group be deleted as a single operation? I think that would 
> fix everything.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to