-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[destination-motherduck] append batch tmp table instead replace during override #50425
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
...e-integrations/connectors/destination-motherduck/destination_motherduck/processors/duckdb.py
Show resolved
Hide resolved
Co-authored-by: Guen Prawiroatmodjo <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add a test that reproduces the issue as well (both for the 50k rows case and <50k rows)?
...e-integrations/connectors/destination-motherduck/destination_motherduck/processors/duckdb.py
Show resolved
Hide resolved
/format-fix
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good! Great job with the quick turnaround for this fix, @marcosmarxm!
What
If your data exceeds 50k, the Motherduck destination will
override
the previous temporary table with the new batch. Since the logic involves dropping and cleaning the table first, we can apply the same logic asappending
because the table is empty.How
Review guide
User Impact
Can this PR be safely reverted and rolled back?