3 ms·
That's not how I read it. I think the arrow-rs team wants a merger, and the arrow2/polars team does not oppose as long as they can keep using the arrow2 API. Th
by dikei 3y ago
That's not how I read it. I think the arrow-rs team wants a merger, and the arrow2/polars team does not oppose as long as they can keep using the arrow2 API. The responsibility to port the changes over would lie with the arrow-rs team, however, as the arrow2/polars team won't spend any effort on it.
- infogulch 3y agoNote that there are about a dozen relevant threads across various repos, which I omitted for obvious reasons. Yes, arrow-rs contributors have driven the effort and made code changes in the arrow-rs repo, but it has absolutely been a collaboration; besides creating new useful apis, arrow2 devs have spent considerable effort to communicate and justify the api differences and the benefits thereof. And switching polars from arrow2 to arrow-rs in the end will not be zero effort. I used neutral language to describe the situation with the explicit intention to avoid spawning unnecessarily divisive commentary here. I don't see how your reading is helpful to understand the broad context.