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.
arrow-js-ffi is a much more memory-efficient option for moving Arrow data from Rust to JS because it doesn't require a full buffer copy on the Wasm side to construct an Arrow IPC buffer.
This is pretty much blocked on apache/arrow-rs#5356 or some workaround to it. Because of the way deck.gl handles GPU-based picking, it can have a maximum of 256 layers because their indices are packed into a single channel. We take great care on the Python side to choose a record batch size that limits the number of pickable layers to a max of 256. But because arrow-rs does its own rechunking, we're left with tons of tiny record batches of 1024 rows each, which blows up deck.gl (this is from the parquet-wasm bump, not related to using arrow-js-ffi).
Also blocked on fixing parquet package exports (ref kylebarron/parquet-wasm#414)