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
If a user publish wrong data/metadata on mqtt those data are written as bufr and amqp2dballed raise an exception.
A check on import level is not so easy because the bufr are grouped in amqp messages.
Python api do not implement an --rejected option as in dbadb import that shoud be a solution. ARPA-SIMC/dballe#258
Rejected messages can be managed with an nack and a "x-dead-letter-exchange" option in rabbitmq queue with a dedicated exchange and queue ...
The text was updated successfully, but these errors were encountered:
related with
ARPA-SIMC/dballe#257
If a user publish wrong data/metadata on mqtt those data are written as bufr and amqp2dballed raise an exception.
A check on import level is not so easy because the bufr are grouped in amqp messages.
Python api do not implement an --rejected option as in dbadb import that shoud be a solution.
ARPA-SIMC/dballe#258
Rejected messages can be managed with an nack and a "x-dead-letter-exchange" option in rabbitmq queue with a dedicated exchange and queue ...
The text was updated successfully, but these errors were encountered: