Skip to content

Conversation

@brknstrngz
Copy link
Contributor

  • we currently replace all slashes in routing keys and message types with dots; this is however not mandated for any other exchange type than 'topic'. This change adds a check that skips the replacement for non-topic exchanges, such as 'direct'
  • add support for the 'headers' exchange type

@brknstrngz brknstrngz changed the title Only enforce dots in routing keys for topic exchanges Bugfix: amqp_0_9 output: only enforce dots in routing keys for topic exchanges Mar 22, 2025
brknstrngz and others added 3 commits March 31, 2025 16:10
- we currently replace all slashes in routing keys and message types
  with dots; this is however not mandated for any other exchange type
  than 'topic'. This change adds a check that skips the replacement
  for non-topic exchanges, such as 'direct'
Signed-off-by: Mihai Todor <todormihai@gmail.com>
@mihaitodor mihaitodor force-pushed the brknstrngz/bugfix/dots_in_routing_keys_for_topic_exchanges branch from c378ccb to db854e4 Compare March 31, 2025 15:30
Copy link
Contributor

@mihaitodor mihaitodor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the contribution @brknstrngz! LGTM

@mihaitodor mihaitodor merged commit c2f95d4 into redpanda-data:main Mar 31, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants