You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: datafusion/wasmtest/README.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,5 +87,13 @@ The following DataFusion crates are verified to work in a wasm-pack environment
87
87
-`datafusion-physical-expr`
88
88
-`datafusion-physical-plan`
89
89
-`datafusion-sql`
90
-
91
-
The difficulty with getting the remaining DataFusion crates compiled to WASM is that they have non-optional dependencies on the [`parquet`](https://docs.rs/crate/parquet/) crate with its default features enabled. Several of the default parquet crate features require native dependencies that are not compatible with WASM, in particular the `lz4` and `zstd` features. If we can arrange our feature flags to make it possible to depend on parquet with these features disabled, then it should be possible to compile the core `datafusion` crate to WASM as well.
90
+
-`datafusion-expr-common`
91
+
-`datafusion-physical-expr-common`
92
+
-`datafusion-functions`
93
+
-`datafusion-functions-aggregate`
94
+
-`datafusion-functions-aggregate-common`
95
+
-`datafusion-functions-table`
96
+
-`datafusion-catalog`
97
+
-`datafusion-common-runtime`
98
+
99
+
The `datafusion-ffi` crate cannot compile for the wasm32-unknown-unknown target because it relies on lzma-sys, which depends on native C libraries (liblzma). The wasm32-unknown-unknown target lacks a standard C library (stdlib.h) and POSIX-like environment, preventing the native code from being compiled.
0 commit comments