jorgecarleitao commented on issue #1176: URL: https://github.com/apache/arrow-rs/issues/1176#issuecomment-1431561957
> That would be fantastic, finding a way to unify our efforts would be amazing Agree. :D > Let me take some time to think about the implications of this and how we might do it in an incremental fashion. incremental fashion 👍 Do let me know if we need a small demo of the current arrow2 design to motivate it or something else. One idea is to wrap arrow2 arrays in arrow-rs newtypes `struct PrimitiveArray<T>(PrimitiveArrayInternal<T>);`, so that arrow-rs users continue to see (almost) the same API; internally we could glue them together via `From<>` implementations - just an idea. > I am willing to run the ["Ip clearance"](https://incubator.apache.org/ip-clearance/) process to get the arrow2 codebase into the arrow-rs repository. I have done this before for object_store and while it takes some time I think it is worth it in this case. Thank you 🙇 - I will certainly help in gathering evidence regarding contributors. > As for the technical plans, the only thing I feel (very) strongly is that there is a migration path that doesn't involve a "all downstream crates need to rewrite the world" @alamb - I agree - I believe ultimately some rewriting will have to happen as we have arrow2 and arrow-rs users with two APIs sometimes with the same name and different signatures. I do think that the way arrow-rs has been re-writing its APIs to be very conductive and productive (i.e. gradually, deprecation warnings, etc.) 🎩 tip to the team here. -- 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]
