You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2019/09/18 09:23:48 UTC

[GitHub] [nifi] VinceCastro commented on issue #3700: NIFI-6638: Empty multiple queues at once at different flow levels

VinceCastro commented on issue #3700: NIFI-6638: Empty multiple queues at once at different flow levels
URL: https://github.com/apache/nifi/pull/3700#issuecomment-532601047
 
 
   Got it! So you suggest to move the empty multiple queues logic from the front-end to the back-end side by adding one or more rest api to the exsisting endpoints. We may have cases where the user wants to empty different selected process groups at once, or different selected queues at once, so I would suggest to add two rest api to the "FlowFile Queues" endpoint: the first one should accept a list of process group IDs in order to empty the queues inside them(recursively or not); the second one should accept a list of connections IDs to empty. We may collect all IDs into a json body.
   
   This way we can efficiently cover all cases where the user wants to:
   
   - empty the selected queue
   - empty the selected queues
   - empty the selected process group (recursively or not)
   - empty the selected process groups (recursively or not)
   - empty the current process group (recursively or not)
   
   What do you think about?
   
   @adarmiento you stated:
   
   > I think that the most useful features are:
   > 
   >> selected queue: empty the selected queue
   >> selected queues: empty the selected queues
   >> current process group (recursive): empty all queues inside the current process group recursively
   
   What if I want to empty only a subset of the flow I'm currently viewing? In that case features like "empty the selected process group" or "empty the selected process groups" are necessary, do you agree?
   
   However, as mentioned by @adarmiento
   > Are there use cases in which you are interested into emptying all queue of a processor group which is not the current one AND at the same time we do not want to delete the queue recursively?
   
   I have doubts about the usefulness of the non recursive actions. Are there use cases where we do not really need to empty a process group recursively? Do you guys @mcgilman @adarmiento suggest to add the non recursive actions or postpone them to another pr?
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services