Hi,
The vote carries with 3 +1 binding votes, no non-binding
vote and no -1 votes.
I'll merge https://github.com/apache/arrow/pull/36009 .
Thanks,
--
ko
In <20230628.103017.2111667987485891680@clear-code.com>
"[VOTE][Format][Flight] Result set expiration support" on Wed, 28 Jun 2023
10:
For better or for worse the Rust implementation requires the underlying buffer
is UTF-8 including null slots, as this allows returning the buffer as a native
string type, which in turn allows kernels to use Rust's native string
functionality. Whilst I agree the specification is ambiguous on this
Le 02/07/2023 à 14:00, Raphael Taylor-Davies a écrit :
More an observation than an issue, but UTF-8 validation for StringArray can be
done very efficiently by first verifying the entire buffer, and then verifying
the offsets correspond to the start of a UTF-8 codepoint.
Caveat: null slots
> I would be interested in hearing some input from the Rust community.
A couple of thoughts:
The variable number of buffers would definitely pose some challenges for the
Rust implementation, the closest thing we currently have is possibly
UnionArray, but even then the number of buffers is stil
> * This is the first layout where the number of buffers depends on the
data
> and not the schema. I think this is the most architecturally significant
> fact. I
I have spent some time reading the initial proposal -- thank you for that.
I now understand what Weston was saying about the "variabl
