-
Notifications
You must be signed in to change notification settings - Fork 128
fix(ds query): isolate temp table names #1321
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
base: main
Are you sure you want to change the base?
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideWhen cloning a dataset query object, the temporary table name list is reset to avoid sharing state across instances by assigning a new empty list in the clone method. Class diagram for updated clone method in dataset queryclassDiagram
class DatasetQuery {
steps
table
temp_table_names
clone(new_table=True)
}
DatasetQuery : clone() resets temp_table_names to []
File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Deploying datachain-documentation with
|
Latest commit: |
33e80f8
|
Status: | ✅ Deploy successful! |
Preview URL: | https://bf9664f0.datachain-documentation.pages.dev |
Branch Preview URL: | https://isolate-temp-table-names.datachain-documentation.pages.dev |
ee46cea
to
be6eeaf
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1321 +/- ##
=======================================
Coverage 88.84% 88.84%
=======================================
Files 155 155
Lines 14240 14241 +1
Branches 2025 2025
=======================================
+ Hits 12652 12653 +1
Misses 1124 1124
Partials 464 464
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Fixes for the tests in separate PR: #1322 |
yep, thanks @dreadatour ... I'll keep looking into this PR ... it is probably right for the current approach with temp tables, but I need to understand the whole temp table mechanics a bit better |
Updated: might also fix #722
When we run multiple joins, within the same chain, due to a recursive line:
in
SQLJoin
(link)we might end up with a list of 8K+ items, with a lot a lot of duplicates.
It means query can run very long at the end.
Script to reproduce this. Mind we run show and save at the end, essentially also means we are doubling the list.
TODO: