> * Python 3.8 wheel's test was failed. It also failed with
> 1.0.0 and 1.0.1.
>
> https://gist.github.com/kou/62cae5dcf4dcdd8f044fd33c50e8a007
Fix: https://github.com/apache/arrow/pull/8477
In <20201015.060219.286366408805956805@clear-code.com>
"Re: [VOTE] Release Apache Arrow 2
The vote carries with 8 +1 votes from the PMC, no -1 votes, and 3
additional +1 votes from the community. Thanks everyone!
We'll work on moving ahead with the IP clearance so that we can get this
merged.
Neal
On Wed, Oct 14, 2020 at 7:46 AM Uwe L. Korn wrote:
> +1 (binding)
>
> On Wed, Oct 14,
I would agree with this.
I’ve been working with the GO Arrow library last few weeks, and took a while to
get head around it all / how to use etc.
Even then not sure i’ve got it right.
Usage examples would be great.
Regards
Mark
> On Oct 14, 2020, at 4:08 PM, Fernando Herrera
> wrote:
>
>
Hi Benjamin,
Nice catch!
The code has been like this for quite some time.
I think one reason is that the 'setBytes' and 'getBytes' APIs
support manipulating data in large batches, so it is less
performance-critical.
IMO, it is reasonable to respect the constant to improve performance.
Best,
Liy
Hi all,
I have a very specific question about the `ArrowBuf` implementation in
the Java project.
There is this constant `BOUNDS_CHECKING_ENABLED` which enables/disables
checking of the bounds when accessing the buffer. However, the
`getBytes` and `setBytes` implementations ignore this constant
Arrow Build Report for Job nightly-2020-10-15-0
All tasks:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-10-15-0
Succeeded Tasks:
- centos-6-amd64:
URL:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-10-15-0-github-centos-6-amd64
- centos-7-aar
