ritchie46 commented on a change in pull request #9778:
URL: https://github.com/apache/arrow/pull/9778#discussion_r603314361
##########
File path: rust/arrow-pyarrow-integration-testing/tests/test_sql.py
##########
@@ -78,3 +78,23 @@ def test_time32_python(self):
del expected
# No leak of C++ memory
self.assertEqual(old_allocated, pyarrow.total_allocated_bytes())
+
+ def test_list_array(self):
+ """
+ Python -> Rust -> Python
+ """
+ old_allocated = pyarrow.total_allocated_bytes()
+ a = pyarrow.array([[1, 2], [1, 2]], pyarrow.list_(pyarrow.int64()))
+ b = arrow_pyarrow_integration_testing.round_trip(a)
+ # list equality does not work, so we check the elements
Review comment:
> Well, then you can also add `assert a.type == b.type` to check if the
nullable flag is correctly set.
This fails. So my question is, is this due to the code in this PR (i.e. on
the Rust side). If so, than I need a bit of guidance of where this should be
defined.
And more general, what is the use of this flag?
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
