-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
ARROW-6158: [C++/Python] Validate child array types with type fields of StructArray #5488
ARROW-6158: [C++/Python] Validate child array types with type fields of StructArray #5488
Conversation
return pyarrow_wrap_array(out) | ||
cdef Array result = pyarrow_wrap_array(out) | ||
result.validate() | ||
return result |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some of the Array.from_..
did such validation in the end, and some not (like StructArray.from_arrays, which I was fixing here), so updated this now for all from_..
constructors
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to add some constructor microbenchmarks just so we understand the cost involved, but in principle this is okay
Codecov Report
@@ Coverage Diff @@
## master #5488 +/- ##
=========================================
Coverage ? 89.23%
=========================================
Files ? 768
Lines ? 112453
Branches ? 0
=========================================
Hits ? 100344
Misses ? 12109
Partials ? 0
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
return pyarrow_wrap_array(out) | ||
cdef Array result = pyarrow_wrap_array(out) | ||
result.validate() | ||
return result |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to add some constructor microbenchmarks just so we understand the cost involved, but in principle this is okay
Thanks, I can look into the microbenchmarks (in the asv benchmark suite right?) |
https://issues.apache.org/jira/browse/ARROW-6158