WIP: Attempt to support arrow serialization #119
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.
This PR is an experiment towards supporting base64-encoded arrow IPC data. The idea is to support data URLs of the form:
Then convert the base64 data to binary and parse using the arrow JavaScript library. Then pass the arrow Table as the
values
property of the dataset. Arrow Tables support the array-of-objects format that Vega uses, so this mostly just works. But I've run into a few issues:vl-convert-rs/tests/vl-specs/circle_binned_b64.vl.json
).Given these issues, I'm not sure it makes sense to move forward with this right now. But wanted to document my findings.