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

How to deal with the existing rows data update and delete case #9

Open
cw1427 opened this issue Apr 10, 2020 · 1 comment
Open

How to deal with the existing rows data update and delete case #9

cw1427 opened this issue Apr 10, 2020 · 1 comment

Comments

@cw1427
Copy link

cw1427 commented Apr 10, 2020

As per the logic mentioned in the README, it just deals with the data increasing case. How to deal with the existing rows data update case and delete case?

@greggles
Copy link

This seems like a feature request to deal with that use case, but it seems like a big change that might not be well suited to this tool. Perhaps this limitation should be mentioned in the README.

A workaround would be to delete the table in bigquery and migrate the data entirely, though that obviously doesn't work well for large amounts of data.

This problem might be best solved with a solution based on change data capture which is its own world of tools/solutions.

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