-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Selector support #2592
Comments
Yes but only after 3.9 when this plugin is rearchitected. |
Ok, thanks for your quick answer. |
Please ask questions on the mailing list. Here's the most recent update. We make no ETA promises but I'd not expect 3.9 before Q4 2019. |
Does this also concern message selectors for queues when used with the JMS client? I rely on them to create consumers that specifically consume messages with high priority, which works well with Apache's ActiveMQ and Artemis, and it would be awesome if RabbitMQ also supported them. |
Does the new server version 4 finally support selectors (JMS filters)? |
@beaver71 4.0 release notes are public. IIRC there were discussions on the team around JMS-related features but they might have been focussed on the client library. RabbitMQ is open source software so anyone can look into investigating what may be missing, propose and design with pros and cons, and if there are no objections, contribute it. |
4.1 will support AMQP filter expressions (for AMQP consumers consuming from streams). The RabbitMQ JMS client supports JMS filters for topics. Filters (whether AMQP or JMS) for queues are tricky to implement in a scalable way, but we are considering implementing them in the future. |
I tried rhea node.js library and in particular this example https://github.com/amqp/rhea/tree/master/examples/selector example but obviously it's not working with RabbitMQ+plugin amqp1.0.
On the contrary it works with several other AMQP 1.0 brokers (ActiveMQ, Qpid cpp, Qpid Java, ...).
Do you plan to support filters, like JMS filters?
The text was updated successfully, but these errors were encountered: