WIP: Improved async api for arrow1 #393
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.
Improvements
Range: bytes=-8
and then secondlyRange: bytes=-9772
for the full metadata (testing in this notebook).table = await parquetFile.read_row_group(0)
made just a single request!AsyncParquetFile
(for Async API refactor #215). I think this is cleaner and easier to use, and on the Rust side the only data stored in the class is the file metadata, arrow schema, and reqwest client. So if the user forgets to call.free()
, not a ton of memory will leak.Todo:
Promise.all
from the JS side? It's probably non-trivial to implement support for this in wasmcc @H-Plus-Time