Skip to content

Conversation

@FlorianLB
Copy link
Contributor

Complement to #94 , some brokers were missing the feature.

@FlorianLB
Copy link
Contributor Author

@s3rius any chance you can review it (and make a release) soon ?

we are missing this feature to build a proper priority queue system

@chandr-andr
Copy link
Member

@FlorianLB Hi! I can, s3rius on the vacation now.

Could you please check tests? They failed.

@chandr-andr
Copy link
Member

@FlorianLB, and please add some information about your PR in the repo's README.

@FlorianLB FlorianLB force-pushed the feat-custom-queue-name-per-message branch from 6341cf2 to fe2bfdf Compare October 6, 2025 10:27
@FlorianLB
Copy link
Contributor Author

@chandr-andr I documented the changes.

But tests are failing because of the test pipeline setup, not due to the changes

@chandr-andr
Copy link
Member

@FlorianLB Ok, thanks! I'll make a release now

@chandr-andr chandr-andr merged commit 0ff98e1 into taskiq-python:main Oct 6, 2025
3 of 8 checks passed
@chandr-andr
Copy link
Member

@FlorianLB https://pypi.org/project/taskiq-redis/1.1.1/
You can check it here

@vkozmik
Copy link

vkozmik commented Oct 21, 2025

@FlorianLB could you please explain how to use it for low priority queue? E.g. how to configure a worker to consider that one queue has bigger priority than the other?

@FlorianLB
Copy link
Contributor Author

FlorianLB commented Nov 12, 2025

@vkozmik

how to configure a worker to consider that one queue has bigger priority than the other?

You can't right now. You have two options with the current state of the library :

  • having X different instances of the worker, each configured for a specific queue
  • with only one worker, use the additional_streams parameter to do a kind of round-robin between the main stream and the additional stream. It's not a true priority system but it works good enough for a case where your low priority queue has way more volume than the default one.

@vkozmik
Copy link

vkozmik commented Nov 12, 2025

Thank you for the information!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants