Changing upload process for lazy loaded DataFrames #165
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…dataframes by batch instead of all into memory at once
…into batch-loading-large-dataframes
AnimatorJoe
force-pushed
the
batch-loading-large-dataframes
branch
from
49f5de7
to
4a421f6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In the original DataFrame upload implementation for Snowflake and PySpark DataFrames, the DataFrames are loaded entire into memory first before being uploaded (PySpark, Snowflake).
However, this can cause problems if the DataFrames are larger than the driver's memory (PySpark, Snowflake).
This PR processes the DataFrames by batch, which solves the memory problem.