Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: export record batch through stream #4806

Merged
merged 2 commits into from
Sep 17, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions arrow-pyarrow-integration-testing/tests/test_sql.py
Original file line number Diff line number Diff line change
Expand Up @@ -393,6 +393,23 @@ def test_sparse_union_python():
del a
del b

def test_tensor_array():
tensor_type = pa.fixed_shape_tensor(pa.float32(), [2, 3])
inner = pa.array([float(x) for x in range(1, 7)] + [None] * 12, pa.float32())
storage = pa.FixedSizeListArray.from_arrays(inner, 6)
f32_array = pa.ExtensionArray.from_storage(tensor_type, storage)
Copy link
Contributor

@tustvold tustvold Sep 11, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just as an observation, it is rather strange to me that extension arrays would be a first-class abstraction and in so doing obfuscate the underlying storage type

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is rather strange to me that extension arrays would be a first-class abstraction and in so doing obfuscate the underlying storage type

I think for systems where RecordBatch is a type exposed to end-users at the interface, the obfuscation is a feature, not a bug.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it is unfortunate that arrow doesn't have a clear separation between logical and physical types. IMO DataType is a physical type, whereas extension types are definitely in the category of logical types, it's a bit of a mess 😅


# Round-tripping as an array gives back storage type, because arrow-rs has
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I must be missing something fundamental here, an array can only have the storage type??

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean because the extension metadata is in the field metadata, and thus separate from the Array? Arrays typically have a DataType associated with it, so this depends on whether your Arrow implementation has an Extension variant of DataType or not. Arrow C++ and arrow2 do, arrow-rs doesn't.

It actually looks like Arrow C++ exports DataType with the extension metadata:

https://github.com/apache/arrow/blob/b7581fee01ed0d111d5a0361c2f05779aa3c33e8/cpp/src/arrow/c/bridge.cc#L189
https://github.com/apache/arrow/blob/b7581fee01ed0d111d5a0361c2f05779aa3c33e8/cpp/src/arrow/c/bridge.cc#L243-L252

So if arrow-rs had an Extension variant of data type, we could do the same and thus arrays themselves could be exported as extension arrays. Of course, that opens whole different can or worms, as discussed in #4472

# no notion of extension types.
b = rust.round_trip_array(f32_array)
assert b == f32_array.storage

batch = pa.record_batch([f32_array], ["tensor"])
b = rust.round_trip_record_batch(batch)
assert b == batch

del b

def test_record_batch_reader():
"""
Python -> Rust -> Python
Expand Down
31 changes: 9 additions & 22 deletions arrow/src/pyarrow.rs
Original file line number Diff line number Diff line change
Expand Up @@ -59,14 +59,14 @@ use std::convert::{From, TryFrom};
use std::ptr::{addr_of, addr_of_mut};
use std::sync::Arc;

use arrow_array::RecordBatchReader;
use arrow_array::{RecordBatchIterator, RecordBatchReader};
use pyo3::exceptions::{PyTypeError, PyValueError};
use pyo3::ffi::Py_uintptr_t;
use pyo3::import_exception;
use pyo3::prelude::*;
use pyo3::types::{PyDict, PyList, PyTuple};
use pyo3::types::{PyList, PyTuple};

use crate::array::{make_array, Array, ArrayData};
use crate::array::{make_array, ArrayData};
use crate::datatypes::{DataType, Field, Schema};
use crate::error::ArrowError;
use crate::ffi;
Expand Down Expand Up @@ -270,25 +270,12 @@ impl FromPyArrow for RecordBatch {

impl ToPyArrow for RecordBatch {
fn to_pyarrow(&self, py: Python) -> PyResult<PyObject> {
let mut py_arrays = vec![];

let schema = self.schema();
let columns = self.columns().iter();

for array in columns {
py_arrays.push(array.to_data().to_pyarrow(py)?);
}

let py_schema = schema.to_pyarrow(py)?;

let module = py.import("pyarrow")?;
let class = module.getattr("RecordBatch")?;
let args = (py_arrays,);
let kwargs = PyDict::new(py);
kwargs.set_item("schema", py_schema)?;
Copy link
Contributor

@tustvold tustvold Sep 11, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why doesn't this work? The schema is provided with the arrays? Is there some limitation of pyarrow's from_arrays method?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basically, PyArrow considers there to be a mismatch if passed a schema with an extension type but the arrays passed are all storage arrays.

I created an issue in PyArrow's tracker to fix this:
apache/arrow#37669

In theory, this code should be fine, so we can consider this a workaround for a bug in PyArrow 😁

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we could link to the upstream bug in the code? So that we can potentially avoid this at some point in the future

let record = class.call_method("from_arrays", args, Some(kwargs))?;

Ok(PyObject::from(record))
// Workaround apache/arrow#37669 by returning RecordBatchIterator
let reader =
RecordBatchIterator::new(vec![Ok(self.clone())], self.schema().clone());
let reader: Box<dyn RecordBatchReader + Send> = Box::new(reader);
let py_reader = reader.into_pyarrow(py)?;
py_reader.call_method0(py, "read_next_batch")
}
}

Expand Down
Loading