> This implies that each canonical alternative layout would codify a
> primary layout as its "fallback."
Yes, that was part of my proposal:
> * A new layout, if it is semantically equivalent to another, is
considered an alternative layout
Or, to phrase it another way. If there is not a
+1 (macOS M1)
Cheers,
-Jacob
On Tue, Jun 6, 2023 at 7:48 PM Sutou Kouhei wrote:
> Hi,
>
> I would like to propose the following release candidate (RC1) of
> Apache Arrow Julia version 2.6.1.
>
> This release candidate is based on commit:
> 2d1114e180ef11f9d3bbe310b2eb856550cfbeb3 [1]
>
> The
+1 (macOS M1)
On Tue, Jun 6, 2023 at 9:48 PM Sutou Kouhei wrote:
> Hi,
>
> I would like to propose the following release candidate (RC1) of
> Apache Arrow Julia version 2.6.1.
>
> This release candidate is based on commit:
> 2d1114e180ef11f9d3bbe310b2eb856550cfbeb3 [1]
>
> The source release
Hi,
I would like to propose the following release candidate (RC1) of
Apache Arrow Julia version 2.6.1.
This release candidate is based on commit:
2d1114e180ef11f9d3bbe310b2eb856550cfbeb3 [1]
The source release rc1 is hosted at [2].
Please download, verify checksums and signatures, run the unit
Thanks Weston. That all sounds reasonable to me.
> with the caveat that the primary layout must be emitted if the user does not
> specifically request the alternative layout
This implies that each canonical alternative layout would codify a
primary layout as its "fallback." This seems
+1 on what Ian said.
And as I write kernels for this new format, I’m learning that it’s possible
to re-use the common infrastructure used by List and LargeList to implement
the ListView related features with some adjustments.
IMO having this format as a second-class citizen would more likely
>From Micah:
> This sounds reasonable to me but my main concern is, I'm not sure there is
> a great mechanism to enforce canonical layouts don't somehow become
default
> (or the only implementation).
I'm not sure I understand. Is the concern that an alternative layout is
eventually
used more
To clarify why we cannot simply propose adding ListView as a new
“canonical extension type”: The extension type mechanism in Arrow
depends on the underlying data being organized in an existing Arrow
layout—that way an implementation that does not support the extension
type can still handle the
With 4 +1 votes (4 binding) the release is approved
The release is available here:
https://dist.apache.org/repos/dist/release/arrow/arrow-rs-41.0.0/
It has also been released to crates.io
Thank you to everyone who helped verify this release
Raphael
On 05/06/2023 16:25, Will Jones wrote:
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.6.1/
It has also been released to crates.io
Thank you to everyone who helped verify this release
Raphael
On 05/06/2023 16:15, Will
10 matches
Mail list logo
