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/20 15:25:29 UTC
[GitHub] [nifi] patricker commented on issue #3700: NIFI-6638: Empty
multiple queues at once at different flow levels
patricker commented on issue #3700: NIFI-6638: Empty multiple queues at once at different flow levels
URL: https://github.com/apache/nifi/pull/3700#issuecomment-533599387
@VinceCastro I'd leave the choice to keep it as a single PR, or split it, up to your comfort level with the back-end code. This is your first contribution, have you looked at the back-end layer?
A few file pointers in case you want to look into this:
- The main end point is in nifi-web-api/org.apache.nifi.web.api.FlowFileQueueResource
- Do a quick search for `@Path("{id}/drop-requests")` and you'll find the end point.
This is a POST for a single Queue. The ID of the queue goes in the URL. You might be able to replace this with the ID of a process group and then do a lookup, but probably easier to create a new end point for `@Path("{id}/process-group-drop-requests`.
But what about submitting multiple queues async? I think you would need another endpoint there too, and have the body of the post contain some JSON describing the list.
Interestingly, the `DropRequestDTO` does not specify which Queue it's for, so you wouldn't need to worry about that part too much. The harder part is probably the actual drop logic in NiFi, and updating the other internal objects like `StandardNiFiServiceFacade.createFlowFileDropRequest`.
----------------------------------------------------------------
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