You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bug occurs when attempting to publish data to a RabbitMQ broker using the AMQP protocol and subscribing to this broker using MQTT in a streaming pipeline. The MageAI publisher creates an incorrect RabbitMQ queue because the exchange passed by default in the code is ' ' (empty string), whereas it should be 'amq.topic'.
Creating a binding on this queue does not solve the problem, hence communication does not happen correctly.
To reproduce
create a rabbitmq exporter in streaming mode.
deploy a rabbitmq broker with rabbitmq_mqtt plugin (rabbitmq-plugins enable --offline rabbitmq_mqtt).
create a rabbitmq mqtt suscriber in python with paho-mqtt.
send data with Mage to Rabbit with AMQP template.
the suscriber will not recive data.
Expected behavior
MageAI template should create the AMQP queue with the correct exchange and the communication would work perfectly.
Screenshots
No response
Operating system
Docker compose version: 3.9
MageAI image: mageai/mageai:0.9.70
Rabbitmq image: rabbitmq:3.9-management
Additional context
Solution:
I create a custom publisher to avoid the bug and creating the communication.
The text was updated successfully, but these errors were encountered:
Mage version
0.9.70
Describe the bug
The bug occurs when attempting to publish data to a RabbitMQ broker using the AMQP protocol and subscribing to this broker using MQTT in a streaming pipeline. The MageAI publisher creates an incorrect RabbitMQ queue because the exchange passed by default in the code is ' ' (empty string), whereas it should be 'amq.topic'.
Creating a binding on this queue does not solve the problem, hence communication does not happen correctly.
To reproduce
Expected behavior
MageAI template should create the AMQP queue with the correct exchange and the communication would work perfectly.
Screenshots
No response
Operating system
Additional context
Solution:
I create a custom publisher to avoid the bug and creating the communication.
The text was updated successfully, but these errors were encountered: