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

Feature: improve how do we specify what tables to listen #178

Open
alarbada opened this issue Jul 1, 2024 · 1 comment
Open

Feature: improve how do we specify what tables to listen #178

alarbada opened this issue Jul 1, 2024 · 1 comment
Labels
feature New feature or request

Comments

@alarbada
Copy link
Contributor

alarbada commented Jul 1, 2024

Feature description

Description

As discussed on the team sync, we might want to improve how do we specify which tables to listen. For example, debezium has these configuration options:

schema.include.list and schema.exclude.list

same for tables

table.include.list and table.exclude.list.

Should we emulate them?

@alarbada alarbada added feature New feature or request triage Needs to be triaged labels Jul 1, 2024
@github-project-automation github-project-automation bot moved this to Triage in Conduit Main Jul 1, 2024
@alarbada alarbada changed the title Feature: allow copying all tables from schema with the source connector Feature: improve how do we specify what tables to listen Jul 1, 2024
@lovromazgon lovromazgon removed the triage Needs to be triaged label Jul 8, 2024
@nickchomey
Copy link

For whatever it is worth, I like this idea a lot. Especially if it has wildcard support. Maxwell's Daemon (for mysql) does something similar https://maxwells-daemon.io/filtering/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants