[REVIEW] Upgrade arrow & pyarrow to 5.0.0 - #8908
Conversation
arrow & pyarrow to 5.0.0arrow & pyarrow to 5.0.0
Codecov Report
@@ Coverage Diff @@
## branch-21.10 #8908 +/- ##
===============================================
Coverage ? 10.58%
===============================================
Files ? 116
Lines ? 19060
Branches ? 0
===============================================
Hits ? 2018
Misses ? 17042
Partials ? 0 Continue to review full report at Codecov.
|
robertmaynard
left a comment
There was a problem hiding this comment.
CMake changes LGTM
brandon-b-miller
left a comment
There was a problem hiding this comment.
The changes in the column constructor lgtm but I am not quite following why all these tests were wrong. Can you help me with a simple example?
|
I'm a bit surprised that CI passes for dask-cudf (I would expect that we need #8871 to avoid the ParquetDataset deprecations in pyarrow-5, but we could be narrowly avoiding the problem for now). Also, note that Dask is temporarily pinned to pyarrow<5 |
Sure, previously arrow had a bug of incorrectly allowing value with a lower precision, in 5.0, this is fixed: >>> pa.array([10, 20], type=pa.decimal128(precision=2, scale=2))
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "pyarrow/array.pxi", line 306, in pyarrow.lib.array
File "pyarrow/array.pxi", line 39, in pyarrow.lib._sequence_to_array
File "pyarrow/error.pxi", line 143, in pyarrow.lib.pyarrow_internal_check_status
File "pyarrow/error.pxi", line 99, in pyarrow.lib.check_status
pyarrow.lib.ArrowInvalid: Decimal type with precision 2 does not fit into precision inferred from first array element: 2If we see here, we cannot fit 10 & 20 into a decimal of precision 2 & scale 2. |
I can confirm I didn't see |
Oh I see. And thus the result precision must be updated as well. Thank you for clarifying! |
|
rerun tests |
|
rerun tests |
|
rerun tests |
2 similar comments
|
rerun tests |
|
rerun tests |
|
@gpucibot merge |
This PR upgrades arrow to
5.0.0.