documentation for multiple queues with the symfony bundle #920
Conversation
|
|
||
| Both ways will enable you to run a queue called `say` exclusively with the [cli command](cli_commands.md) `bin/console enqueue:consume say` or run all tasks except those in the `say` queue with `bin/console enqueue:consume --skip=say` | ||
|
|
||
| Beware that messages for this topic will end up in the router queue first - so if you don't have a process running that consumes the router queue, your messages will never _really_ reach the `say` queue. In that case you'll still have to run `bin/console enqueue:consume default` - or, if you have changed the name of your router queue: `bin/console enqueue:consume router` |
There was a problem hiding this comment.
The command accepts several queues
It would be good to suggest users use
bin/console enqueue:consume say default
with clarifications on why default should be there
Other than that it looks great! Thank you @lostfocus for your work.
There was a problem hiding this comment.
Life got into the way, sorry. :) I'll clear it up later.
There was a problem hiding this comment.
Okay, I've re-read my paragraphs and I'm not all that sure why default should be there. I figured that with two queue runners - one only running the say queue and the other one running all and/or only the default default - everything should be fine?
| use Enqueue\Client\CommandSubscriberInterface; | ||
| use Interop\Queue\Processor; | ||
|
|
||
| class SayHelloProcessor implements Processor, TopicSubscriberInterface |
There was a problem hiding this comment.
fyi: you don't have to implement TopicSubscriberInterface interface if you use enqueue.processor tag.
There was a problem hiding this comment.
If you implement TopicSubscriberInterface then a tag is not needed as the service is autoconfigured with enqueue.topic_subscriber tag.
|
This is really missing from the documentation. Helped me a lot, thanks :) |
|
Sorry @balabis, this PR kinda got lost :) @lostfocus, would you mind revisiting this? |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This docs saved me a lot of time - it should be officially merged definitely! |
As mentioned in #919 - and in #806 and #838
There is not really any new information on this page but it should answer this pretty common question which I have found unanswered previously both here and on StackOverflow.