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

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

Commit 0d7edcb3ace95e8729c4bc27457d702fdd879f09 in nifi's branch 
refs/heads/NIFI-259 from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=0d7edcb ]

NIFI-108:
- Removing sort from UI.
- Addressing issues with listing and flowfile retrieval when clustered.
- Making the context menu item available when source and destination are still 
running.
- Adding a refresh button to the queue listing table.
- Fixing the flowfile summary sorting in the cluster manager.
- Adding a message when the source or destination of a connection is actively 
running.
- Updating the documentation regarding queue interaction.
- Updating the error message when a flowfile is no longer in the active queue.
- Updated queue listing to allow listing to be done while source and 
destination are running but not sort or have ability to search
- Added heartbeat when we finish clearing queue
- Addressing comments from review.


> DFM should be allowed to inspect/interact with FlowFiles on a Connection
> ------------------------------------------------------------------------
>
>                 Key: NIFI-108
>                 URL: https://issues.apache.org/jira/browse/NIFI-108
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Core Framework, Core UI
>            Reporter: Matt Gilman
>            Assignee: Matt Gilman
>             Fix For: 0.5.0
>
>         Attachments: NIFI-108_Purge-List_Queue_Flow.xml, nifi-108.dump
>
>
> User should be able to see the attributes, as well as download the content 
> for flowfiles in the top of the active queue.
> Additional tickets have been created and linked for searching, removing, and 
> uploading flowfiles in a given queue.



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

Reply via email to