[
https://issues.apache.org/jira/browse/DRILL-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venki Korukanti updated DRILL-4714:
-----------------------------------
Description:
Currently ODBC/JDBC drivers spawn a set of queries on INFORMATION_SCHEMA for
metadata. Client has to deal with submitting a query, reading query results and
constructing required objects. Sometimes same work is done twice (planning work
in case of prepare statements) to get the metadata and execute query. Instead
we could simplify the client by providing APIs on the client interface and let
the server construct the required objects and send them to client directly.
These APIs provide common info that can be consumed by the JDBC/ODBC driver.
[Here|https://docs.google.com/document/d/1ytwGDYGbEFuS3_eUEqRikh7wQABFyHjS0fXJ6wr1eSU/edit?usp=sharing]
is the doc explaining the new APIs.
was:
Currently ODBC/JDBC drivers spawn a set of queries on INFORMATION_SCHEMA for
metadata. Client has to deal with submitting a query, reading query results and
constructing required objects. Sometimes same work is done twice (planning work
in case of prepare statements) to get the metadata and execute query. Instead
we could simplify the client by providing APIs on the client interface and let
the server construct the required objects and send them to client directly.
These APIs provide common info that can be consumed by the JDBC/ODBC driver.
Will attach a doc explaining the new APIs.
> Add metadata and prepared statement APIs to DrillClient<->Drillbit interface
> ----------------------------------------------------------------------------
>
> Key: DRILL-4714
> URL: https://issues.apache.org/jira/browse/DRILL-4714
> Project: Apache Drill
> Issue Type: New Feature
> Reporter: Venki Korukanti
>
> Currently ODBC/JDBC drivers spawn a set of queries on INFORMATION_SCHEMA for
> metadata. Client has to deal with submitting a query, reading query results
> and constructing required objects. Sometimes same work is done twice
> (planning work in case of prepare statements) to get the metadata and execute
> query. Instead we could simplify the client by providing APIs on the client
> interface and let the server construct the required objects and send them to
> client directly. These APIs provide common info that can be consumed by the
> JDBC/ODBC driver.
> [Here|https://docs.google.com/document/d/1ytwGDYGbEFuS3_eUEqRikh7wQABFyHjS0fXJ6wr1eSU/edit?usp=sharing]
> is the doc explaining the new APIs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
