Another possibility I'd like to float is doing this in ADBC first? My primary
motivation is (1) from Joris's list: I'd like to bump a few components
(Snowflake, maybe SQLite) to a "stable" version while leaving the others
behind, and in this context I think it'd be much more helpful to users to
I tend to agree with Dewey. Using run-end-encoding to represent a scalar
is clever and would keep the c data interface more compact. Also, a struct
array is a superset of a record batch (assuming the metadata is kept in the
schema). Consumers should always be able to deserialize into a struct
ar
Thank you for the background!
I still wonder if these distinctions are the responsibility of the
ArrowSchema to communicate (although perhaps links to the specific
discussions would help highlight use-cases that I am not envisioning).
I think these distinctions are definitely important in the cont
With 4 +1 votes (3 binding) the release is approved.
Thank you everyone who helped with this release (likely to be the last on
the arrow list).
Success! The release is available here:
https://dist.apache.org/repos/dist/release/arrow/arrow-datafusion-37.1.0
It has also been released to crates.i
With 4 +1 votes (4 binding) the release is approved
The release is available here:
https://dist.apache.org/repos/dist/release/arrow/arrow-object-store-rs-0.10.0/
It has also been released to crates.io
Thank you to everyone who helped verify this release
On 18/04/2024 17:38, vin jake wrote: