hi Andy -- yes. I'll send out the vote thread shortly
On Tue, Jan 22, 2019 at 8:27 AM Andy Grove wrote:
>
> Wes,
>
> With the 0.12 release out, could we now start the vote for the DataFusion
> donation?
>
> Thanks,
>
> Andy.
>
> On Tue, Jan 15, 2019 at 8:16 AM Andy Grove wrote:
>
> > Wes,
> >
>
Wes,
With the 0.12 release out, could we now start the vote for the DataFusion
donation?
Thanks,
Andy.
On Tue, Jan 15, 2019 at 8:16 AM Andy Grove wrote:
> Wes,
>
> I went ahead and created a JIRA (
> https://issues.apache.org/jira/browse/ARROW-4263) and PR (
>
Wes,
I went ahead and created a JIRA (
https://issues.apache.org/jira/browse/ARROW-4263) and PR (
https://github.com/apache/arrow/pull/3399) for the donation so it is ready
to go if the vote passes.
Thanks,
Andy.
On Mon, Jan 14, 2019 at 1:57 PM Andy Grove wrote:
> Wes,
>
> Thanks. Yes, I'd
Wes,
Thanks. Yes, I'd like to proceed with the vote as soon as you are ready.
I don't think I need much time at all at this point to prepare the merge. I
already have a branch of DataFusion that is building against the latest
Arrow code, so it's really just a case of updating source files with
Getting the 0.12 release out is my priority right now, but it seems
that there are no major objections to this code donation.
@Andy -- I can kick off the vote to accept the code donation in the
next few days if you'd like to proceed with that. How much time do you
think it would take for you to
Wes,
Thanks. This sounds great.
Andy.
On Tue, Jan 8, 2019 at 8:28 AM Wes McKinney wrote:
> hi Andy -- I'm supportive of the code donation. I see building
> in-memory, embeddable analytics and query processing as the natural
> next stage of this project. As I have described on this mailing
Hi Neville,
Thanks for the support.
DataFrame and SQL are two different ways of building a logical query plan
and it makes sense that they should both build the same type of plan
without code duplication. It is also sometimes beneficial to mix and match
DataFrame and SQL operations (as per
hi Andy -- I'm supportive of the code donation. I see building
in-memory, embeddable analytics and query processing as the natural
next stage of this project. As I have described on this mailing list,
I intend to work on this with my colleagues in C++ with the goal of
making such functionality
Hi Andy,
I can't comment on the voting process, but regarding the addition of
DataFusion:
I support the idea to donate the code, mainly as I think that will help us
accelerate some work on Rust. Out of curiousity, I've been prototying a
'Rust dataframe' abstraction which (can/will) have various
Bumping this thread ... I know everyone is busy with getting the 0.12
release out, but would be good to know the process for raising this for a
vote. However, given the lack of comments on this thread I'm starting to
suspect that maybe there isn't much of an appetite for this, which is fine,
but
Thanks, Ted!
I wish I'd been a bit more specific about my ask in the original email... I
guess my question (for Wes?) is what is the process to raise this for a
vote?
Andy.
On Sun, Jan 6, 2019 at 2:59 PM Ted Dunning wrote:
> Cool!
>
>
>
> On Sun, Jan 6, 2019 at 1:52 PM Andy Grove wrote:
>
Cool!
On Sun, Jan 6, 2019 at 1:52 PM Andy Grove wrote:
> I'm starting a new thread for this discussion (this was previously
> discussed in the Rust Roadmap thread).
>
> The reason I got involved with Arrow is that I have been working on
> DataFusion[1] which is currently an in-process SQL
I'm starting a new thread for this discussion (this was previously
discussed in the Rust Roadmap thread).
The reason I got involved with Arrow is that I have been working on
DataFusion[1] which is currently an in-process SQL query engine on top of
Arrow. It allows queries to be executed against
13 matches
Mail list logo
