Polars uses Arrow2 in their code. So should this lib #393
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi! This PR is mostly about compatibility with Polars.
With this, using
return_type="polars"will have the same result aspolars.from_sqlBoth Polars itself and their integration with this lib uses Arrow2.
Reference to the integration: https://github.com/pola-rs/polars/blob/9dabbe5b4d0d21a65bf6e2a52062175485603a86/py-polars/polars/io.py#L1096
Also, for the from_arrow function, I believe testing the current API and then falling back to the old one should be preferable. But I can remove this from the PR if you disagree.