Update coding-practice-trips-by-week-asset.md #23819
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adapt the solution to address the requirement of not loading the full data into memory.
Summary & Motivation
The challenge asks to design the code assuming that the whole trips data does not fit into memory but a week of data does. When fetching data from the database, the previous solution did the good job of filtering week data, but then went on to append this data to a initially empty dataframe. That approach would still find the same memory overflow.
How I Tested These Changes
Defined a trips by week asset in the local project following the Dagster University Course and successfully materialized it.
Changelog [New | Bug | Docs]
NOCHANGELOG