-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
heads up: Arrow API updates and breaking changes #38
Comments
Thanks! We noticed the changes last week and were wondering when they were targeted to be released. |
@nmichaud we're sitting down for a code-review this afternoon. Assuming that goes well, we'll call for a release vote shortly after, which would mean likely release this weekend or early next week. I can update this thread when I have more information if you'd like. |
@trxcllnt that would be great! We definitely depend on the eagerly allocated columns list in our integration - will need to take a deeper look into the changes in the new version. |
Thanks for the fix! |
Moved the getChartElement helper into a new module
Hey guys, we're getting ready to release Arrow JS 0.3.0 soon and want to give you a heads up on breaking changes. We refactored things a bit to align better with the C++ implementation, and make it easier to implement the Arrow Writer APIs (coming soon).
I'm just looking at perspective.js#L281, but haven't searched the rest of the perspective codebase so there may be more places to update.
Table
now exposes its SchemaRemoved the eagerly-allocated
columns
list from the Table, in favor of lazily allocating columns viagetColumnAt(i)
. You can map the schema's fields to get the columns:Removed the
vector.name
property, now accessible via the schema (Vectors can be combined in ways that they differ from the original schema, in which any tie to the originalfield
metadata isn't necessarily valid anymore)Added DataType classes so now all the vector type information from the schema is available and strongly-typed at runtime. Now the
vector.type
field will refer to this instance. We also export the DataType classes and enums on theArrow.type
namespace, so you can do enum orinstanceof
comparisons.Added
TypeVisitor
andVectorVisitor
classes, to make it easier to walk the schema and vector trees:That's all I can think of for now. We have a repo where we push new releases for testing and use ahead of the apache release vote, so feel free to link to this in your package.json if you want to test it out: https://github.com/graphistry/arrow
Best,
Paul
The text was updated successfully, but these errors were encountered: