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] db_sync table sync incremental/full will fail when trying to copy over an empty table #1136

Open
austinweisgrau opened this issue Sep 15, 2024 · 0 comments
Labels
bug Impact - something is currently broken in Parsons and needs to be fixed

Comments

@austinweisgrau
Copy link
Collaborator

The db_sync module does not handle well the scenario where the source table is empty, and in most cases will result in a confusing error being raised (destination table does not exist). This is due to trying to run a row count at the end of the sync. Even if running an incremental sync with verify_row_count explicitly set to false, if the source table is empty, the sync reverts to a full sync and does not pass along the verify_row_count flag.

Detailed Description

To Reproduce

Your Environment

  • Version of Parsons used (if you know):
  • Environment name and version (e.g. Chrome 39, node.js 5.4):
  • Operating System and version (desktop or mobile):

Additional Context

Add any other context about the problem here.

Priority

Please indicate whether fixing this bug is high, medium, or low priority for you. If the issue is time-sensitive for you, please let us know when you need it addressed by.

@austinweisgrau austinweisgrau added the bug Impact - something is currently broken in Parsons and needs to be fixed label Sep 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Impact - something is currently broken in Parsons and needs to be fixed
Projects
None yet
Development

No branches or pull requests

1 participant