Closed (fixed)
Project:
Queue UI
Version:
3.2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
10 May 2024 at 20:42 UTC
Updated:
21 Oct 2024 at 07:04 UTC
Jump to comment: Most recent
I have an application with more than 300 (and counting) derivative queues, making Queue UI difficult to use.
Create a derivative queue.
Group derivative queues in the UI under a base queue worker umbrella, and allow to be inspected and processed as a single queue.
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
aaronbaumanNot sure what I was looking at, but the item count for subqueues looks fine in fact.
Comment #3
volegerCan you provide an example of a derivative queue definition for a test case?
Comment #4
aaronbaumanHere's the deriver i'm using for the curious:
This deriver then gets referenced in the @Cron annotation field of my existing cron queue worker:
And I have another procedure to insert queue items with a queue name like
media_analysis:$nidwhich then get processed by the queue worker, thanks to Derivative API.The derivative is mostly useful so that I can more easily prevent duplicate queue items, but it breaks the Queue UI pretty badly.
I started looking at adapting Queue UI, but it's a bit of a can of worms - will require special handling for every route and callback that uses the {queueName} placeholder, for starters.
So IMO it's fine to leave this issue on Postponed, and I'll implement a custom UI for my special case.
Comment #5
volegerSo, you expect to see a separate view based on the selected base derivative worker definition, right? I see that as a separate route with the same table rener approach for the overview page, but queues are created based on the selected derivative.
I'll prepare the MR with the approach I see so you can try it out.
Comment #7
voleger@aaronbauman, please try patching the 3.2.x version of the queue_ui module with the diff of MR. Let me know whether it is a usable iteration for now.
I'm okay with the current implementation and will add the functional test coverage. However, I need feedback on the current version of the feature.
Comment #9
volegerI added test coverage for grouping. It has to be stable. In case of any issues, create a follow-up.