Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
The queue functionality should work for ANY queue, not just Redis. Lets refactor this to just be queue agnostic
Issue fork usage_data-3261184
Show commands
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:
- 3261184-general-queue
changes, plain diff MR !12 - 3261184-refactor-queue-logic changes, plain diff MR !9
Comments
Comment #4
b_sharpe commentedComment #5
b_sharpe commentedI have some concerns with how this works. The queue system is meant to work without knowledge of it's backend, we should be following this as well.
What ideally we'd see here is just a selection of "Use Queue API to process usage data" as an option per UsageType plugin, in which when checked items are put into the queue and then are processed by our worker without knowledge of which backend is doing the queuing.
Queue workers will always be Drupal, but the queue backend should be up to the developer in control of such settings. Obviously our preference is not database here, as the whole point is to prevent DB interaction on every page tracking usage, which is why Redis was originally targeted.
Comment #10
b_sharpe commentedAwesome, Thanks!