search

rabbitmq / rabbitmq-mqtt

RabbitMQ MQTT plugin
https://www.rabbitmq.com/mqtt.html
Other
174 stars 68 forks source link

Message holding user_id property #205

Closed miili closed 5 years ago

miili commented 5 years ago

Hi there,

we are publishing to the MQTT endpoint and consume AMQP downstream. Is it intended behaviour that user_id and timestamp property are not set?

Best, M

michaelklishin commented 5 years ago

Thank you for your time.

Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. GitHub issues are not used for questions, investigations, root cause analysis, discussions of potential issues, etc (as defined by this team).

We get at least a dozen of questions through various venues every single day, often light on details. At that rate GitHub issues can very quickly turn into a something impossible to navigate and make sense of even for our team. Because GitHub is a tool our team uses heavily nearly every day, the signal/noise ratio of issues is something we care about a lot.

Please post this to rabbitmq-users.

Thank you.

michaelklishin commented 5 years ago

RabbitMQ does not set either of those fields. rabbitmq_message_timestamp can set the timestamp. Username is validated but not set.

Neither of those fields exists in MQTT 3.1.1, so the behavior is what it is in AMQP 0-9-1 by default.