Skip to content

Shovel: for AMQP 1.0 sources, message properties are not propagated #2745

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

Closed
michaelklishin opened this issue Jan 25, 2021 · 5 comments
Closed
Assignees

Comments

@michaelklishin
Copy link
Collaborator

This C# example demonstrates publishing of an AMQP 1.0 message with custom application properties. When a Shovel with an AMQP 1.0 source consumes it, it will not propagate the properties to the destination.

@woppa684
Copy link

Apart from the custom application properties, also not all standard AMQP1.0 properties (see the spec) are propagated. For example "subject" is missing, although the spec states:

The properties section is part of the bare message; therefore, if retransmitted by an intermediary, it MUST remain unaltered.

@MistarzJan
Copy link

Hey, is there any ETA/progress on this issue? @michaelklishin

@michaelklishin
Copy link
Collaborator Author

Besides the fact that by 3.11 or 3.12 AMQP 1.0 will be the message container used internally by RabbitMQ for all protocols, I don't have much to share. We do not offer ETA, this is open source software. If you want something done, contribute it.

@michaelklishin
Copy link
Collaborator Author

michaelklishin commented Jan 18, 2024

Message containers in 3.13 largely addresses this (or at least revisit and clarify the translation mechanism greatly), if any specific properties are missing, please file new specific issues.

@michaelklishin
Copy link
Collaborator Author

#7508 is highly relevant, too.

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

3 participants