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

The deletion operation will not be synchronized, only the addition and modification operations will be synchronizedA short description of the bug #6929

Closed
qzl965678745 opened this issue Jan 3, 2023 · 4 comments
Labels
bug Bug report stale

Comments

@qzl965678745
Copy link

After the source database deletes the database table, pull the source database again synchronously. It is found that the deleted database table still exists in the datahub. If it is ensured that the database table of the source data is deleted and then synchronized again, it will not exist in the datahub

@qzl965678745 qzl965678745 added the bug Bug report label Jan 3, 2023
@jjoyce0510
Copy link
Collaborator

Hi there! Thanks for reporting. We are looking into this. My guess is that this is on a source where stateful ingestion is enabled?

@hsheth2
Copy link
Collaborator

hsheth2 commented Jan 3, 2023

I believe this will be fixed by #6877. Deletion synchronization requires stateful ingestion to be enabled.

@github-actions
Copy link

github-actions bot commented Feb 3, 2023

This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io

@github-actions github-actions bot added the stale label Feb 3, 2023
@github-actions
Copy link

github-actions bot commented Mar 5, 2023

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug report stale
Projects
None yet
Development

No branches or pull requests

3 participants