quinnj commented on a change in pull request #272:
URL: https://github.com/apache/arrow-julia/pull/272#discussion_r776181901
##
File path: .asf.yaml
##
@@ -0,0 +1,42 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.
quinnj commented on a change in pull request #272:
URL: https://github.com/apache/arrow-julia/pull/272#discussion_r776181151
##
File path: .asf.yaml
##
@@ -0,0 +1,42 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.
kou commented on a change in pull request #272:
URL: https://github.com/apache/arrow-julia/pull/272#discussion_r776180085
##
File path: .asf.yaml
##
@@ -0,0 +1,42 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See
kou opened a new pull request #272:
URL: https://github.com/apache/arrow-julia/pull/272
fix #271
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
kou opened a new issue #271:
URL: https://github.com/apache/arrow-julia/issues/271
We can configure this repository's metadata by `.asf.yaml`. See also:
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features
We should change at least notification configurations.
kou opened a new issue #270:
URL: https://github.com/apache/arrow-julia/issues/270
JuliaData/Arrow.jl has been transferred to apache/arrow-julia.
See also: #265 and https://issues.apache.org/jira/browse/INFRA-22663
We discussed the development process for apache/arrow-julia on
This is very nice. Look forward to trying it out. One should get
performance improvements on hardware with better interconnects, so
performance just with TCP is not illustrative of all cases.
On 12/28/21 11:41 PM, David Li wrote:
Thanks for the feedback!
Collective operations:
Thanks for the feedback!
Collective operations: unfortunately, these look very different from the model
Flight provides (which is just RPC). If there's interest, we could consider
implementing or exposing them in the future, or looking at making sure Arrow's
IPC APIs play well with the MPI
Le 28/12/2021 à 20:09, David Li a écrit :
Antoine/Micah raised the possibility of extending gRPC instead. That would
be preferable, frankly, given otherwise we'd might have to re-implement a
lot of what gRPC and HTTP2 provide by ourselves. However, the necessary
proposal stalled and was
@david
I think this is really interesting and a really good starting point. :-)
Like Keith said, this paves way to use shared memory execution backends. In
our experience at Cylon, these backends give good scalability for data
engineering jobs.
While send/ receive arrow payloads is essential, I
I ended up drafting an implementation of Flight based on UCX, and doing some
of the necessary refactoring to support additional backends in the future.
It can run the Flight benchmark, and performance is about comparable to
gRPC, as tested on AWS EC2.
The implementation is based on the UCP
The paper[1] is helpful. Compression may also be helpful - but it may be
difficult to standardize this.
[1] https://vldb.org/pvldb/vol12/p2022-chattopadhyay.pdf
On 12/25/21 5:37 AM, Micah Kornfield wrote:
What exactly are you looking for? To my knowledge neither Capacitor nor
Artus have
+1
Thanks,
Jorge
On Fri, Dec 24, 2021 at 3:21 AM Wang Xudong wrote:
> +1 (non-binding)
>
> Happy holidays
>
> ---
> xudong
>
> Andy Grove 于2021年12月24日周五 09:19写道：
>
> > +1 (binding)
> >
> > Thanks,
> >
> > Andy.
> >
> > On Thu, Dec 23, 2021 at 2:26 PM Andrew Lamb
> wrote:
> >
> > > Hi,
> > >
To finish up this thread, the rustsec advisory has been updated:
https://github.com/rustsec/advisory-db/pull/1131
On Tue, Nov 30, 2021 at 5:10 PM Andrew Lamb wrote:
> Well, I finally have a PR[1] that adds full ArrayData validation ready
> for review Any thoughts or review comments would be
14 matches
Mail list logo
