Skip to content
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

feat: allow more flexibility in subject name config #38

Open
ctessier opened this issue Jul 3, 2024 · 1 comment
Open

feat: allow more flexibility in subject name config #38

ctessier opened this issue Jul 3, 2024 · 1 comment

Comments

@ctessier
Copy link

ctessier commented Jul 3, 2024

Hi!

First, thank you for this tool! Very useful!

I would like the ability to configure the subject name (routing key) more precisely, in particular be able to:

  • not have the exchange name at the beginning of the topic
  • be able to opt-out for the schema_table suffix

I would imagine something along this line:

exchange: my.exchange
topic: wal-listener
topicSuffix: true

# => Exchange: my.exchange / Subject: wal-listener.public_myTable
exchange: my.exchange
topic: wal-listener
topicSuffix: false

# => Exchange: my.exchange / Subject: wal-listener

What do you think?
I could find a way to contribute if you'd like ;)

@ihippik
Copy link
Owner

ihippik commented Jul 19, 2024

Hi Clément! Thanks for the kind words!
Could you please explain me your idea, what is the main goal for these changes?
regarding the table name in the topic - do you want to process all messages in one place? actually we can do this using mapping, but it will definitely not be convenient for large volumes

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

No branches or pull requests

2 participants