Hi Aldrin,
Appreciate for these details! Really helpful for understanding.
The good feedback is those connections are dashed out immediately after the
internal rows are deleted.
Wish the new design can reduce such confusion.
Cheers,
Bob
Date: Tue, 8 Dec 2015 19:19:16 -0700
From: ml-node+s39713n5698...@n7.nabble.com
To: bob.zhao.w...@live.com
Subject: Re: [UI Bug] delete route of RouteOnAttribute processor
Bob,
The error indicates that there were files in the queue. This is as
expected in terms of how connections are handled as these connections are
the queues that hold the actual FlowFiles as they progress through their
flow. A FlowFIle "passes through" a processor as it moves from one
connection to one or more output connections. As part of the core
framework, we do not allow connections with FlowFiles enqueued. If you are
running a version of 0.4.0-SNAPSHOT, we have added the ability to perform a
manual flushing of a queue. If not, look forward to that feature coming up
in the 0.4.0 release (which is currently in an RC vote). In this case, you
can also empty that connection by setting an expiration on the connection,
or by moving this connection to another processor to flush it out such as
an UpdateAttribute with its success relationship auto-terminated.
One important distinction is that of a processor's relationships and their
associated connections. The core idea, is that while the connections are
associated to a given relationship, they also exist as separate components
in their own right. You should have noticed a change in format for the
connection(s) for the deleted relationship(s) to a dashed line. If not,
that is certainly not as intended and additional details on how to recreate
it would be great to help us out in fixing any issues.
Thanks for digging in and reporting your findings. Please let us know if
you have any other questions or concerns about this or anything else.
On Tue, Dec 8, 2015 at 6:05 PM, Bob ZHao <[hidden email]> wrote:
> Hello,
>
> I build a working flow for testing. After finish the test, I decide to
> remove some conditional branches in *RouteOnAttribute* processor, so I just
> delete some property rows inside the processor. Then when I close the
> processor window and try to delete the according relations which linked to
> the processor, I get errors and the relation can't be removed.
>
> /*Queue not empty for
>
> Connection*[ID=05ca2b96-18b6-49ac-a68d-b0d00b2784f1,Name=,Source=RouteOnAttribute[id=9f8b022b-bbaf-4de2-ad6d-f107eb89fefc],Destination=PutFile[id=ec5dd052-b6f8-4963-90f9-c2fdf9a85239],Relationships=[output3]/
>
> It's my first time to see this error. But if I delete relations first, it
> works well.
>
> Thanks,
> Bob
>
>
>
>
> --
> View this message in context:
> http://apache-nifi-developer-list.39713.n7.nabble.com/UI-Bug-delete-route-of-RouteOnAttribute-processor-tp5693.html
> Sent from the Apache NiFi Developer List mailing list archive at
> Nabble.com.
>
If you reply to this email, your message will be added to the
discussion below:
http://apache-nifi-developer-list.39713.n7.nabble.com/UI-Bug-delete-route-of-RouteOnAttribute-processor-tp5693p5698.html
To unsubscribe from [UI Bug] delete route of RouteOnAttribute
processor, click here.
NAML
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/UI-Bug-delete-route-of-RouteOnAttribute-processor-tp5693p5708.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
