PyO3 bridge for pyarrow interoperability / fix arrow integration test#691
PyO3 bridge for pyarrow interoperability / fix arrow integration test#691kszucs merged 8 commits intoapache:masterfrom
Conversation
arrow/src/pyarrow.rs
Outdated
There was a problem hiding this comment.
Implementing the conversion traits either on ArrayRef or T: Array is not possible, so I sticked with ArrayData but implemented the PyArrowConvert trait on the array types and ArrayRef for convenience.
Codecov Report
@@ Coverage Diff @@
## master #691 +/- ##
==========================================
- Coverage 82.43% 82.39% -0.05%
==========================================
Files 168 168
Lines 47340 47396 +56
==========================================
+ Hits 39027 39050 +23
- Misses 8313 8346 +33
Continue to review full report at Codecov.
|
kszucs
changed the title
arrow/src/pyarrow.rs
Outdated
There was a problem hiding this comment.
We need to unwrap here because IntoPy is infallible, see PyO3/pyo3#1813
arrow/src/pyarrow.rs
Outdated
There was a problem hiding this comment.
Perhaps we should split it into two conversion traits: TryFromPyArrow and TryIntoPyArrow ?
|
I feel I could review the Rust part of this code for basic hygiene (and what I looked at looks good) but I don't understand the nuances with |
|
@jorgecarleitao addressed the review comments and fixed the python integration test. |
jorgecarleitao
left a comment
jorgecarleitao
left a comment
There was a problem hiding this comment.
Lgtm. Thanks @kszucs !
|
Thanks Jorge! Merging it then. |
| flatbuffers = { version = "=2.0.0", optional = true } | ||
| hex = "0.4" | ||
| comfy-table = { version = "4.0", optional = true, default-features = false } | ||
| prettytable-rs = { version = "0.8.0", optional = true } |
There was a problem hiding this comment.
@kszucs Was this (re)added by mistake or is it intentional?
There was a problem hiding this comment.
looks like it? prettytable-rs should have been replaced by prettyprint.
There was a problem hiding this comment.
Mistake, sorry about that! Created a PR to remove it #737
alamb
changed the title
| lhs_offsets[lhs_start].to_usize().unwrap(), | ||
| rhs_offsets[rhs_start].to_usize().unwrap(), | ||
| (lhs_offsets[len] - lhs_offsets[lhs_start]) | ||
| (lhs_offsets[lhs_start + len] - lhs_offsets[lhs_start]) |
There was a problem hiding this comment.
The code/bug in question appears to have been introduced in apache/arrow#8541 (and thus is also in arrow 5.0, and thus does not need to be backported directly into arrow 5.x) -- I was worried I had backported a bug into arrow 5.3 which needed a fix backported anyways
6 participants
Which issue does this PR close?
Closes #.
Rationale for this change
Motivation comes from apache/datafusion#856 (comment)
PyO3 provides conversion traits between rust and python types. Using the arrow-rs types in the datafusion python bindings required a lot of boilerplate though we could just simply annotate the right type in the function signature and let PyO3 to do the majority of the work.
The error handling should be improved.
What changes are included in this PR?
Are there any user-facing changes?