You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Andy Grove <an...@nvidia.com> on 2020/10/01 00:58:36 UTC
Re: [FlightRPC] Add a "Flight SQL" extension on top of FlightRPC
Sure, I can look at this in the next day or two and will provide feedback.
Thanks,
Andy.
On 9/29/20, 5:54 PM, "Ryan Nicholson" <rn...@gmail.com> wrote:
External email: Use caution opening links or attachments
Hello Andy and Wes,
Thanks for reaching out.
Later this week I have time freeing up to start on Flight-SQL. Would either
of you mind examining the approach in the POC [1] as described in the
"Proof of Concept" section of the proposal document [2]?
I would certainly be happy to chat about this with anyone interested in
participating too.
Thank you,
Ryan
[1] https://github.com/ryannicholson/arrow/pull/2
[2]
https://docs.google.com/document/d/1WQz32bDF06GgMdEYyzhakqUigBZkALFwDF2y1x3DTAI
On Tue, Sep 29, 2020 at 8:52 AM Andy Grove <an...@gmail.com> wrote:
> I am also interested in helping with this effort.
>
> Andy.
>
> On Mon, Sep 28, 2020, 1:58 PM Wes McKinney <we...@gmail.com> wrote:
>
> > hi Ryan,
> >
> > I'm interested in enabling this effort to move forward -- is there any
> > part where feedback or other help could be useful?
> >
> > Thanks,
> > Wes
> >
> > On Wed, Sep 2, 2020 at 4:45 PM Wes McKinney <we...@gmail.com> wrote:
> > >
> > > I haven't been able to scrutinize the details greatly, but I am
> > > supportive of this effort, otherwise we may end up with many database
> > > systems and vendors implementing Flight in different ways. It would be
> > > nice if there was a built-in SQL client layer that we ship in C++ (and
> > > its bindings), Java, and others.
> > >
> > > On Wed, Sep 2, 2020 at 10:24 AM Ryan Nicholson <rn...@gmail.com>
> > wrote:
> > > >
> > > > Hello everyone,
> > > >
> > > > Here is a link to the slides
> > > > <
> >
> https://docs.google.com/presentation/d/1JcOKA1yKYTNodQl5Z1BtK3dhJLx-Vu_RSAqWF_wiJH8/edit?usp=sharing
> > >
> > > > I would like to discuss this morning.
> > > >
> > > > Take care,
> > > > Ryan Nicholson
> > > >
> > > > On Tue, Sep 1, 2020 at 4:02 PM Ryan Nicholson <rn...@gmail.com>
> > wrote:
> > > >
> > > > > Thank you to all who have viewed and given feedback in the posted
> > material
> > > > > so far. I am working on responses as well as preparing some
> material
> > which
> > > > > I would like to share for discussion in the sync call tomorrow. I
> > will post
> > > > > the material here ahead of time.
> > > > >
> > > > > Take care,
> > > > > Ryan Nicholson
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Aug 31, 2020 at 2:21 PM Ryan Nicholson <
> rnicholson@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > >> Hello everyone,
> > > > >>
> > > > >> I would like to propose the following specification to ease
> > adoption of
> > > > >> SQL based clients and backends while leveraging data streams for
> > > > >> transporting data. This specification entails a series of protobuf
> > messages
> > > > >> to be used in the opaque messaging framework payloads to enable
> > browsing of
> > > > >> database metadata and statement style operations with scaffolding
> > available
> > > > >> to help implementers provide logic for their backend.
> > > > >>
> > > > >> Please take a look at the following material:
> > > > >>
> > > > >> - ARROW-9825 <https://issues.apache.org/jira/browse/ARROW-9825
> >
> > has
> > > > >> more details around the goals of the proposal.
> > > > >> - Flight SQL Proposal
> > > > >> <
> >
> https://docs.google.com/document/d/1WQz32bDF06GgMdEYyzhakqUigBZkALFwDF2y1x3DTAI/edit?usp=sharing
> >
> > is
> > > > >> a more detailed document describing new messages and how they
> > would be used.
> > > > >> - https://github.com/ryannicholson/arrow/pull/2 on my Arrow
> fork
> > > > >> shows a sample implementation with a catalog browsing action
> and
> > a prepared
> > > > >> statement query workflow. There are details in the proposal
> > linking to
> > > > >> specific areas of the PR.
> > > > >>
> > > > >> Thank you for your time,
> > > > >> Ryan Nicholson
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> >
>