hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-18240) support getClientInfo/setClientInfo in JDBC
Date Fri, 08 Dec 2017 01:43:00 GMT

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

Sergey Shelukhin commented on HIVE-18240:
-----------------------------------------

Added the description, I will resubmit this for HiveQA once that is working.

> support getClientInfo/setClientInfo in JDBC
> -------------------------------------------
>
>                 Key: HIVE-18240
>                 URL: https://issues.apache.org/jira/browse/HIVE-18240
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-18240.patch
>
>
> These are JDBC APIs that allow the user of the driver to provide client info to the server;
the list of the fields supported by the driver is returned as a result set by getClientInfoProperties
API.
> I've looked at IBM, Oracle, MS etc. docs and it seems like ApplicationName is a common
one; there's also ClientHostname, etc. that we don't need because HS2 derives them already.
> The client will then set these properties via setClientInfo if desired. Whether it is
desired by any BI tools of significance I've no idea. 
> The properties are sent to the server on connect (which is what Microsoft seems to do,
but in Hive model it's impossible because HiveConnection connects in ctor), or on the next
query (I don't recall where I've seen this), or immediately (which is what I do in this patch).
> The getClientInfo API on the driver side seems completely pointless, so I cache clientinfo
locally for it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message