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

Refactor the inputs to use DuckDB as much as possible #706

Closed
3 tasks done
Tracked by #701 ...
clizbe opened this issue Jul 29, 2024 · 0 comments
Closed
3 tasks done
Tracked by #701 ...

Refactor the inputs to use DuckDB as much as possible #706

clizbe opened this issue Jul 29, 2024 · 0 comments
Assignees
Labels
Type: epic Epic issues (collection of smaller tasks towards a goal)
Milestone

Comments

@clizbe
Copy link
Member

clizbe commented Jul 29, 2024

Wherever we have table_tree (df) try to use DuckDB. This should take out TODO in create_internal_structures.
Use DuckDB directly to calculate the weight as sum of the mapping in the RepresentativePeriod.

Sub-issues:

@clizbe clizbe mentioned this issue Jul 29, 2024
52 tasks
@clizbe clizbe changed the title Refactor the inputs to use DuckDB as much as possible. Wherever we have table_tree (df) try to use DuckDB. This should take out TODO in create_internal_structures. Refactor the inputs to use DuckDB as much as possible Jul 29, 2024
@clizbe clizbe added this to the M3 - End Sept milestone Jul 29, 2024
@datejada datejada added the Type: epic Epic issues (collection of smaller tasks towards a goal) label Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: epic Epic issues (collection of smaller tasks towards a goal)
Projects
None yet
Development

No branches or pull requests

3 participants