[
https://issues.apache.org/jira/browse/NIFI-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15087488#comment-15087488
]
Joseph Witt commented on NIFI-108:
----------------------------------
[~mcgilman][~markap14] I gave it a whirl and this is a good step forward.
However, while sorting is very useful the provenance repository is probably the
right off-line place to do that. Interacting with the queue necessarily
requires locking access to the queue and a user would not and should not expect
them viewing the queue to cause any performance degradation. Also the original
motivation here is to see what is active on the queue. The sorting features
and so on are great ideas but the downsides of providing them are too great.
Also, as it stands right now this requires the user to stop the source and
destination processors of that connection. That in my opinion is simply too
great of a cost for this to serve the common case. It limits the uses to while
one is building the flow and in very specific troubleshooting cases.
By simplifying this greatly we can allow the flow to keep running and support
the main use case which is to view the live queue. We should let the user know
that the results may vary while viewing a live/active queue. If they *want* to
stop the source/destinations they certainly can but we do not want to force
them to.
Now, having said all of this I think the path this presently lays down provides
some really useful user experience powers for future consideration but the
implementation needs to be very different (driven on offline provenance data
rather than the in-band live data itself).
Thanks
> 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)
