Micah/Wes,
Yes, I've been following the rust proposal thread with great interest. I do
think that provides a great path forward: transferring the
JuliaData/Arrow.jl repo to apache/arrow-julia would help to solve the
"package history" technical challenges that in part led to the current
setup and
I don't think we need to do anything other than wait until GitHub
fixes this notification bug.
I've been getting them for a week plus because of a mention on an
archery commit, but I don't recall this ever happening over the years.
It seems suspicious that both Wes & Micah, and I would all of a
If there are no more comments on this maybe we should update the original
RFC PR and ensure we are OK with it in principle (Dmitry do you want to do
this or should we start a new PR)? I can try to work on the C++/Python and
Java code in the next few weeks.
On Sun, Apr 4, 2021 at 1:35 PM Micah
I think there are three options:
1. Add it in with the existing type_traits code.
2. Make the definition only in the code you are working on (I'm not sure
if this would be generatelly applicable?)
3. Don't use enable_if_* traits but instead use your own enable_if and
have an "OR" expression
Hi,
I would like to have a variant of arrow::enable_if_number good for
numerical types, boolean as well as Date32 but not any other type so that I
don’t have to repeat template specializations with essentially the same code.
What’s the canonical way to achieve that?
Ying
I added a gmail filter for the offending commit hash. I created a Jira
issue to scrub these @-mentions (in the merge script) from the PR
descriptions in the future.
On Sun, Apr 11, 2021 at 10:31 PM Micah Kornfield
wrote:
> I accidentally merged some commits that "@" mention me and others. This
I accidentally merged some commits that "@" mention me and others. This
seems to have the effect of me getting emails every time someone
forks/syncs the main repo.
Two comments/questions:
1. Please make sure commit messages do not contain @ mentions of people.
2. Does anyone know of a way of
>
> Continuing to grow the community is important, so
>
I would recommend that the most active contributors compensate for
> this with higher level discussions (e-mails / google documents) that
> get circulated on the mailing list, or GitHub issues. I would be
> concerned about using GitHub issues
On Sat, Apr 10, 2021 at 4:07 PM Micah Kornfield wrote:
>
> >
> > Ok, I've had a chance to discuss with a few other Julia developers and
> > review various options. I think it's best to drop the Julia code from the
> > physical apache/arrow repo. The extra overhead on development, release
> >
I'm supportive of this if it addresses most of the issues that folks
in the Rust community have been having.
A handful of thoughts
* Small nit: the DataFusion repository probably needs to be called
apache/arrow-datafusion, so that all repos related to the Arrow TLP
have a common prefix. Example:
Thanks, Andrew. I think I'm done now with the changes I needed to make to
docs and CI.
On Sun, Apr 11, 2021 at 4:13 AM Andrew Lamb wrote:
> Sounds good --- just let us know if you need any help!
>
> Andrew
>
> On Sat, Apr 10, 2021 at 9:48 AM Andy Grove wrote:
>
> > Now that Ballista is merged
I took the first pass at writing a brief blog post for the Ballista
donation. Feedback welcome.
https://github.com/apache/arrow-site/pull/100
Le 10/04/2021 à 23:06, Weston Pace a écrit :
Nightly build triage (based on nightly builds from 4/9):
Failed Tasks:
- conda-linux-gcc-py36-aarch64:
ARROW-12324 (conda builds timing out, conda slow)
- conda-linux-gcc-py37-aarch64:
ARROW-12324 (conda builds timing out, conda slow)
-
Sounds good --- just let us know if you need any help!
Andrew
On Sat, Apr 10, 2021 at 9:48 AM Andy Grove wrote:
> Now that Ballista is merged into the Arrow repo, there is some follow-up
> work around CI and updating documentation.
>
> Given that Apache Arrow follows a Commit-then-review
14 matches
Mail list logo
