Separate io_func from ReadParquet._plan for better caching
#367
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
phofl
reviewed
Oct 27, 2023
rjzamora
commented
Oct 27, 2023
phofl
approved these changes
Oct 27, 2023
|
Thx |
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.
Right now, column projection will invalidate our
ReadParquet._plancache. There is no reason for this to happen, because the column projection does not actually affect the partitioning plan (it only affects the arguments toParquetFunctionWrapper).This PR separates the
ParquetFunctionWrapper(used as theio_func) fromReadParquet._plan.This change is partially related to #365