Skip to content
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

Support wildcards in MQTT topic filters matching retained messages #8824

Open
ansd opened this issue Jul 10, 2023 · 4 comments
Open

Support wildcards in MQTT topic filters matching retained messages #8824

ansd opened this issue Jul 10, 2023 · 4 comments

Comments

@ansd
Copy link
Member

ansd commented Jul 10, 2023

MQTT spec:

the Server MUST send the retained messages matching the Topic Filter of the subscription to the Client

However, RabbitMQ does not send retained messages for Topic Filters containing wildcards.

@robertsLando
Copy link

A future RabbitMQ release will replicate retained messages in the cluster and also send retained messages matching topic filters containing wildcards.

Does this issue also takes track also of the first part about the retained messages that are not replicated in the cluster? In my case this is a big limitation, is there any work in progress or ETA for that?

@ansd
Copy link
Member Author

ansd commented Feb 28, 2024

Does this issue also takes track also of the first part about the retained messages that are not replicated in the cluster?

No, this is tracked in #8096

is there any work in progress or ETA for that?

No. For the time being you can write your own plugin as for example done in https://github.com/gery0815/rabbitmq-mqtt-retained-msg-redis

@robertsLando
Copy link

@ansd Thanks for that! Is there any mongodb alternative? Otherwise we could create one

cc @getlarge

@ansd
Copy link
Member Author

ansd commented Feb 28, 2024

Is there any mongodb alternative?

I'm not aware of a mongodb plugin.

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

No branches or pull requests

2 participants