You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2015/11/01 04:23:27 UTC

[jira] [Commented] (NIFI-730) Purge Queue from UI

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

Aldrin Piri commented on NIFI-730:
----------------------------------

Right you are about the notification.  Didn't even notice the different text.  Good thinking :D

> Purge Queue from UI
> -------------------
>
>                 Key: NIFI-730
>                 URL: https://issues.apache.org/jira/browse/NIFI-730
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework, Core UI
>            Reporter: Brian Ghigiarelli
>            Priority: Minor
>             Fix For: 0.4.0
>
>         Attachments: blocked-ui.dump
>
>
> Making changes to connections between NiFi processors is difficult when data is queued up between those processors. A workaround to this data build up is to stop both processors, reduce/set the FlowFile Expiration of the connection to a low number (e.g., 2 sec), then start the receiving processor to age off the data.
> A more user-friendly solution is to provide a "Purge" or "Delete" context menu option on the queues to remove the data and/or age it off immediately.



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