[
https://issues.apache.org/jira/browse/NIFI-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083889#comment-15083889
]
ASF subversion and git services commented on NIFI-108:
------------------------------------------------------
Commit c7700128b7dc5bd20f48677f4b5c57ddbc01ff26 in nifi's branch
refs/heads/NIFI-108 from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=c770012 ]
NIFI-108: Fixed bug that caused the listFlowFiles operation to wait on a
readLock before returning and performing work asynchronously; fixed bug in
Write-Ahead FlowFile Repository that caused ContentClaims to be queued up for
destruction instead of ResourceClaims - this caused millions of ContentClaims
to be queued up instead of a single ResourceClaim in some tests
> 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
> and possibly remove an item from the queue (destroy the FlowFile entirely).
> Users should also be able to upload a new object into the queue (as requested
> at an apache nifi DC/MD/VA meetup).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
