tustvold commented on issue #1176: URL: https://github.com/apache/arrow-rs/issues/1176#issuecomment-1447931537
What do people think of migrating the arrow2 arrays to be newtypes around the statically typed ArrayData once ready, i.e. much like we are doing for the arrow-rs arrays? This would have a few advantages: * Work can start on merging the codebases without having to wait for IP clearance, I hope to have a first cut of the ArrayData ready for the release in just under two weeks * Allows for incremental changes to arrow2, in much the same vein as we are doing for arrow-rs * We can find potential integration issues sooner * We can immediately divide and conquer * Avoids issues with overloaded method and type names, etc... each codebase can keep its current array abstractions as is, gradually migrating as/when desired I don't really see a way to avoid doing something similar to this, without a break-the-world arrow2 release, and I think bringing this forward has some compelling advantages? -- 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]
