[
https://issues.apache.org/jira/browse/DRILL-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891367#comment-15891367
]
Jinfeng Ni commented on DRILL-5301:
-----------------------------------
[~laurentgo]
PR #764 contains 5 commits, including the patches for DRILL-4994 and
DRILL-4730, which also show up in PR#613.
What commits should I use for DRILL-4994/DRILL-4730 ( the commits in PR#764, or
PR#613), or they are same?
Thanks,
> 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)
