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] Implement JavaScript-compatible implementation #15352
Comments
Dan Robinson / @danrobinson: +1 to TypeScript (another reason I would scrap most of that old repo). |
Brian Hulette: TypeScript does seem like the way to go for this. |
Rick Fanta: I'm esp. interested in getting cool projects like this to work with Arrow (https://github.com/nicolaskruchten/pivottable). [i.e. Super cool but begging for higher quality I/O that Arrow would provide.] |
Wes McKinney / @wesm: |
Brian Hulette: Its still pretty rough around the edges, but it does add the ability to read the arrow file format in the browser and with Node. |
Wes McKinney / @wesm: |
Brian Hulette / @TheNeuralBit: |
Wes McKinney / @wesm: |
Wes McKinney / @wesm: |
I would really like to see an implementation of Arrow that is compatible with NodeJS and modern web browsers. This would enable streaming columnar data to the browser without an intermediate conversion to JSON – I could imagine web-based data visualization systems would benefit substantially from this functionality.
Because Google's Flatbuffers library has first-class JS support, this should be achievable. Carlos Scheidegger created a prototype implementation of the Feather file format (basically: mini-Arrow) last year: https://github.com/wesm/feather/tree/master/js
This JIRA can be an umbrella issue for the JS implementation. As soon as we find interested contributors to work on this, we can create JIRAs and attach them to this issue until we reach a certain level of maturity.
Without starting a bike shed discussion, I humbly request that the implementation be done in TypeScript https://www.typescriptlang.org/
Reporter: Wes McKinney / @wesm
Assignee: Paul Taylor / @trxcllnt
Related issues:
Note: This issue was originally created as ARROW-541. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: