Support building object_store and parquet on wasm32-unknown-unknown target#2896
Conversation
object_store and parquet on wasm32-unknown-unknown target
There was a problem hiding this comment.
FYI compiling with lz4 appears to fail
|
Trying to compile object_store with non-default features returns an error about getrandom which appears related to https://docs.rs/getrandom/latest/getrandom/#webassembly-support I'm not familiar enough with WASM to know if this is an issue or not? |
* Added cargo check step to parquet workflow for wasm32-unknown-unknown * Added compile-time warning for unsupported cloud features when compiling with wasm32 * Added cargo check features to the parquet github workflow. * Added a section to the README.md for parquet
da40737 to
b141ded
Compare
|
Yep, |
|
Benchmark runs are scheduled for baseline = 4d5d10d and contender = f812d2c. f812d2c is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
…wn target (apache#2896) * Support building object_store on wasm32-unknown-unknown target * Added cargo check step to parquet workflow for wasm32-unknown-unknown * Added compile-time warning for unsupported cloud features when compiling with wasm32 * Added cargo check features to the parquet github workflow. * Added a section to the README.md for parquet * * Added wasm32-unknown-unknown section to the object_store README.md

Which issue does this PR close?
Closes #180.
Rationale for this change
My goal is to get
datafusionbuilding and running on thewasm32-unknown-unknowntarget, and gettingobject_storeandparquetare the first steps.What changes are included in this PR?
This PR adds some conditional compilation in
object_store(mostly around disabling local filesystem access), as well as shifting some dependencies to dev, and removing un-used features in deps (i.e. tokio).Are there any user-facing changes?
None expected, this is purely a build-support change.