You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/27 17:42:45 UTC
[jira] [Commented] (DRILL-5301) Add server metadata API

    [ https://issues.apache.org/jira/browse/DRILL-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886202#comment-15886202 ] 

ASF GitHub Bot commented on DRILL-5301:
---------------------------------------

GitHub user laurentgo opened a pull request:

    https://github.com/apache/drill/pull/764

    DRILL-5301: Server metadata API

    Add a Server metadata API to the User protocol, to query server support of various SQL features.
    
    Add support to the client (DrillClient) to query this information.
        
    Add support to the JDBC driver to query this information, if the server supports the new API, or fallback to the previous behaviour (rely on Avatica defaults) otherwise.
    
    Add support to the Server metadata API to the C++ client if available. If the API is not supported to the server, fallback to the previous hard-coded values.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/laurentgo/drill laurent/server-meta

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/764.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #764
    
----
commit 48bf728c88b8244c0fc51ae8856d0f786bd9e986
Author: Laurent Goujon <la...@dremio.com>
Date:   2016-11-04T20:31:19Z

    Refactor DrillCursor
    
    Refactor DrillCursor to be more self-contained.

commit 6583d69df3b972270e146e53ab2ddcf9c4aff93c
Author: Laurent Goujon <la...@dremio.com>
Date:   2016-11-04T20:32:44Z

    DRILL-4730: Update JDBC DatabaseMetaData implementation to use new Metadata APIs
    
    Update JDBC driver to use Metadata APIs instead of executing SQL queries

commit 17ce38a44d098e744620a28b25c93fd352e7c76d
Author: Laurent Goujon <la...@dremio.com>
Date:   2016-11-05T00:36:42Z

    DRILL-4994: Add back JDBC prepared statement for older servers
    
    When the JDBC client is connected to an older Drill server, it always
    attempted to use server-side prepared statement with no fallback.
    
    With this change, client will check server version and will fallback to the
    previous client-side prepared statement (which is still limited to only execute
    queries and does not provide metadata).

commit 5048bb650bf3a42e9f7920727e19e33ae59f0188
Author: Laurent Goujon <la...@dremio.com>
Date:   2017-02-24T23:41:07Z

    DRILL-5301: Server metadata API
    
    Add a Server metadata API to the User protocol, to query server support
    of various SQL features.
    
    Add support to the client (DrillClient) to query this information.
    
    Add support to the JDBC driver to query this information, if the server supports
    the new API, or fallback to the previous behaviour (rely on Avatica defaults) otherwise.

commit d912267efad379e3730f800bc7b3af57bee2aa06
Author: Laurent Goujon <la...@dremio.com>
Date:   2017-02-26T18:23:59Z

    DRILL-5301: Add C++ client support for Server metadata API
    
    Add support to the Server metadata API to the C++ client if
    available. If the API is not supported to the server, fallback
    to the previous hard-coded values.
    
    Update the querySubmitter example program to query the information.

----


> Add server metadata API
> -----------------------
>
>                 Key: DRILL-5301
>                 URL: https://issues.apache.org/jira/browse/DRILL-5301
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components:  Server, Client - C++, Client - Java, Client - JDBC, Client - ODBC
>            Reporter: Laurent Goujon
>            Assignee: Laurent Goujon
>
> JDBC and ODBC clients exposes lots of metadata regarding server version and support of various parts of the SQL standard.
> Currently the returned information is hardcoded in both clients/drivers which means that the infomation returned is support as of the client version, not the server version.
> Instead, a new method should be provided to the clients to query the actual server support. Support on the client or the server should be optional (for example a client should not use this API if the server doesn't support it and fallback to default values).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)