drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5301) Add server metadata API
Date Thu, 02 Mar 2017 00:39:45 GMT

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

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

Github user jinfengni commented on the issue:

    https://github.com/apache/drill/pull/764
  
    Which JIRA should the last commit (Refactor DrillCursor) belong to, DRILL-4994, 4730,
OR 5301?
      


> 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
>              Labels: ready-to-commit
>
> 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)

Mime
View raw message