paleolimbot commented on issue #151: URL: https://github.com/apache/sedona-db/issues/151#issuecomment-3334203899
Thank you for opening! I think we'd love to make build SedonaDB for WASM. There are a few things to consider: - Figuring out exactly what WASM thing to build. Is it a CLI REPL? A Python package for Pyodide? A full Node.js binding like DuckDB? - Getting the native dependencies to build. The last time I tried to build the Python package for pyiodide I wasn't able to get one of the native dependencies to recognize the cross-compilation flags for emscripten. I imagine this is possible given projects like https://github.com/datafusion-contrib/datafusion-wasm-playground , but also those projects focus on the planning rather than execution. - Ensuring we can execute things/handle the async runtime. Some of @james-willis ' early experiments returned errors when actually executing queries - Cloud IO. None of the objstore filesystems build for WASM (er, I wasn't able to build them for wasm), so we'd have to run everything through Python HTTP IO. Not a problem, but possibly a lot of work. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
