Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Receive message properties
See original GitHub issueThis receiver only consumes the body portion of the message but we often need to read some extra metadata from a RabbitMQ message like the headers or the routing key. It would be great if we could get a DStream of a RabbitMQMessage with message properties and headers.
I can submit a PR if you want.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Message Headers and Properties | Microsoft Learn
If a single message is sent or received, then these properties are contained in the BrokerProperties HTTP header in a JSON-encoded format. If...
Read more >ReceiveMessage - Amazon Simple Queue Service
These attributes include: All – Returns all values. ApproximateFirstReceiveTimestamp – Returns the time the message was first received from the queue ...
Read more >Receive Message Event - Appian 22.4
The Receive Message event allows you to receive that message, trigger events based on the message properties, and store the message properties for...
Read more >IBM MQ - Message properties
Message properties are used by message selectors to filter publications to topics or to selectively get messages from queues. Message properties can be...
Read more >Set and Get Message Properties
Before a client sends a message, it can use a "set property" method to set the message properties. The client can check the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @pedroszattoni @fpousserot @jrglee and @stephaneseng the PR have been merged now, thanks all for the job, in special to @stephaneseng
Hello @stephaneseng. A while ago, manege to modify the receiver, so that it returns tuples of messages body and routing keys, which was what I needed. Even so, I appreciate your contribution. Thank you.