I agree. Segfaults are not nice.
I can take it. I would possibly need some guidance.
Best,
Jorge
On Thu, May 13, 2021 at 12:52 AM Neal Richardson <
neal.p.richard...@gmail.com> wrote:
> Hi,
> As discussed at the biweekly sync call, I wanted to gauge interest in doing
> a 4.0.1 patch release.
Hi,
As discussed at the biweekly sync call, I wanted to gauge interest in doing
a 4.0.1 patch release.
There currently are 14 issues in JIRA tagged with 4.0.1 [1]. There are 3
segfaults, including one that a cuDF maintainer raised yesterday [2] in
requesting a patch release.
I don't want to bias
Attendees:
Jim Apple
Ian Cook
Nic Crane
Prem Sagar Gali
Jonathan Keane
Micah Kornfield
David Li
Rok Mihevc
Niranda Perera
Eduardo Ponce
Gyan Prakash
Neal Richardson
Aster Rosa
Naman Udasi
Discussion:
* Interval type: Micah is working on implementations in C++ and Java. Note
that Parquet uses uns
+1 (non binding)
Thanks!
This is going to make quite some users / maintainers happy.
On Wed, May 12, 2021, 23:23 Andrew Lamb wrote:
> Thank you -- I am expecting that the first few times will have some bumps
> and that we'll optimize the process accordingly after that
>
> On Wed, May 12, 2021 a
Thank you -- I am expecting that the first few times will have some bumps
and that we'll optimize the process accordingly after that
On Wed, May 12, 2021 at 9:45 AM Wes McKinney wrote:
> +1. I will add that I'm supportive of abbreviated votes for the
> biweekly releases, so if you get the votes
Le 12/05/2021 à 21:19, Weston Pace a écrit :
The parquet format has a "field id" concept (unique integer identifier
for a column) that gets promoted in the C++ implementation to a
key/value pair in the field's metadata.
I don't think anything says the "field id" should be unique. It's just
a
The parquet format has a "field id" concept (unique integer identifier
for a column) that gets promoted in the C++ implementation to a
key/value pair in the field's metadata. This has led me to a few
questions around how this field (or metadata in general) interacts
with higher level APIs.
1)
At
Having a way to encode sorting (and distribution) information is something
I'd also be very interested in. If provided in a standardized format, this
would enable optimizations across multiple Arrow-based systems. So I'd be
happy to get involved in this!
Best,
Hendrik
On Wed, 12 May 2021 at 00:25
Hi all,
Our biweekly call is coming up at the top of the hour at
https://meet.google.com/vtm-teks-phx. All are welcome to join. Notes will
be shared with the mailing list afterward.
Neal
Since ARROW-12739 is a binary/dyadic elementwise function (taking
(string, string) -> list), it makes sense to implement as a
compute function / ScalarKernel.
I agree that some utility functions that we have may be able to be
reframed as compute functions. Speaking of which, we might consider
prom
+1. I will add that I'm supportive of abbreviated votes for the
biweekly releases, so if you get the votes in a 24 hour window, then
releasing to crates.io sounds fine to me. For major releases with
breaking changes, allowing the full 72 hours seems prudent.
On Tue, May 11, 2021 at 11:02 PM Jorge
Arrow Build Report for Job nightly-2021-05-12-0
All tasks:
https://github.com/ursacomputing/crossbow/branches/all?query=nightly-2021-05-12-0
Failed Tasks:
- conda-win-vs2017-py36-r36:
URL:
https://github.com/ursacomputing/crossbow/branches/all?query=nightly-2021-05-12-0-azure-conda-win-vs20
12 matches
Mail list logo
