wjones127 commented on issue #3540:
URL: https://github.com/apache/arrow-rs/issues/3540#issuecomment-1416646288
I'm actually having second thoughts about putting this in the arrow-rs repo.
Having it here has some benefits:
* Gets released along with other arrow-rs crates, so it will be kept
up-to-date with the quick release cycle.
* Is in a repo that has a lot of Rust reviewers.
But if we put it in arrow-adbc:
* It's easier to integration test with the other ADBC components.
* It wouldn't be tied to arrow-rs, and so we could potentially support both
arrow-rs and arrow2 through feature gates. Only parts of the API have Arrow
code, and much of the FFI interface doesn't, so having a common implementation
for both Arrow implementations isn't crazy. And I think this is important
because I hope to help integrate the driver manager with Polars.
@alamb What are your thoughts on these tradeoffs? Am I missing anything?
--
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]
