-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[js] Are there plans to support Parquet as a data format? #2209
Comments
It's a good-sized project because of the dependency stack involved (Thrift, various compression libraries) and because Parquet itself is a somewhat complex file format. I opened https://issues.apache.org/jira/browse/ARROW-2786 so the feature can be tracked there |
Thanks. There's some existing work under an MIT license or similar variant here. It doesn't work for me, as it attempts to compile LZO, and it seems I don't have the right dev environment configured for that -- but it might be a useful start, or have some useful tidbits. |
Ah, interesting. LZO isn't really used anymore (as soon as Snappy came around people largely stopped using it because of the *GPL licensing issues) |
Was there any progress made on this? |
None yet. The JIRA is still open and there is some discussion of alternatives (e.g. 3rd party parquet libraries, using the rust parquet implementation via wasm) but as far as I can glean from the mailing list there is no one working on a native JS parquet implementation within Apache Arrow. There is ongoing JS work (I believe they even had a virtual meetup in February) being discussed on the mailing list so if this is something you are interested in working on I would recommend reaching out on the dev mailing list. |
Others have reported that this library supports in-browser reading of Parquet files: https://github.com/kbajalc/parquets |
Title pretty much says it all. I'm using Javascript, and would like to be able to read/write (read, mainly) Parquet data. I know it's not currently available, but is this a planned feature?
The text was updated successfully, but these errors were encountered: