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

Bug: ensure existing publications publish for the configured tables #145

Open
lyuboxa opened this issue May 9, 2024 · 1 comment
Open
Labels
bug Something isn't working

Comments

@lyuboxa
Copy link
Contributor

lyuboxa commented May 9, 2024

Bug description

When the connector is started with a publication that is pre-created, the published tables are not matched to the configured tables. If a replication slot is created on the publication it can produce records for an unexpected tables or none of the expected tables.

Steps to reproduce

  1. Create tables t1, t2, t3
  2. Create pub_t1_t2 publication for t1, t2
  3. Start connector configured to use pub_t1_t2 but table t3
  4. See records changes be published.

Version

latest

@lyuboxa lyuboxa added bug Something isn't working triage Needs to be triaged labels May 9, 2024
@github-project-automation github-project-automation bot moved this to Triage in Conduit Main May 9, 2024
@simonl2002 simonl2002 moved this from Triage to Todo in Conduit Main May 13, 2024
@simonl2002 simonl2002 removed the triage Needs to be triaged label May 13, 2024
@hariso hariso moved this from Todo to Triage in Conduit Main Aug 19, 2024
@raulb
Copy link
Member

raulb commented Aug 19, 2024

Hey @lyuboxa ! Today during the Conduit sync we wondered whether you were still planning on working on this, or we should leave it for a future milestone. Thank you!

@maha-hajja maha-hajja removed the status in Conduit Main Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

3 participants