Use arrow library for checkpoint parquet file read/write #20
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
chelseajonesr
commented
Jul 24, 2023
| github.com/segmentio/encoding v0.3.5 // indirect | ||
| golang.org/x/sys v0.5.0 // indirect | ||
| ) | ||
|
|
||
| replace github.com/segmentio/parquet-go v0.0.0-20230427215636-d483faba23a5 => github.com/chelseajonesr/parquet-go v0.0.3 | ||
| replace github.com/apache/arrow/go/v13 => github.com/chelseajonesr/arrow/go/v13 v13.0.0-20230711200800-c7890b0a2007 |
There was a problem hiding this comment.
This redirection is for a minor patch to allow Arrow to skip serializing/deserializing records to Arrow when the tag is "-", similarly to JSON. It's been accepted into the Arrow 14 branch as of today so I'll likely remove this redirection in the optimization branch that is in progress,
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.
Use the Arrow library for checkpoint read/write.
Note that while this is already much faster and more memory efficient at loading large checkpoints than the previous version, it's still using a very large amount of memory on very large checkpoints (73GB on a 24 million row checkpoint). An optimization branch is in progress.