[
https://issues.apache.org/jira/browse/ARROW-9825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286236#comment-17286236
]
Andy Grove commented on ARROW-9825:
-----------------------------------
Proposal:
https://docs.google.com/document/d/1WQz32bDF06GgMdEYyzhakqUigBZkALFwDF2y1x3DTAI
Slides:
https://docs.google.com/presentation/d/1JcOKA1yKYTNodQl5Z1BtK3dhJLx-Vu_RSAqWF_wiJH8
> [FlightRPC] Add a "Flight SQL" extension on top of FlightRPC
> -------------------------------------------------------------
>
> Key: ARROW-9825
> URL: https://issues.apache.org/jira/browse/ARROW-9825
> Project: Apache Arrow
> Issue Type: New Feature
> Components: FlightRPC, Format
> Reporter: Ryan Nicholson
> Priority: Major
>
> As a developer of database clients and backends, I would like to have a
> standard in place to communicate between the two while being able to leverage
> the data transfer features of Arrow Flight.
> The Arrow Flight RPC specification allows for extensibility by using opaque
> payloads to perform “Actions”, specify “Commands” and so on.
> I propose the addition of a Flight SQL extension consisting of predefined
> protobuf messages and workflows to enable features such as:
> * Discovering specific database capabilities from generic clients
> * Browsing catalogs.
> * Execution of different types of SQL commands.
> Supporting documentation and a POC changelist will be sent to the mailing
> list in the coming days which describes protobuf messages and workflows
> enabling these features.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
