[jira] [Commented] (HIVE-18240) support getClientInfo/setClientInfo in JDBC

["Juliusz Sompolski (Jira)" <ji...@apache.org>]

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

Juliusz Sompolski commented on HIVE-18240:
------------------------------------------

It seems that up until ~2017, the protocol version of Thriftserver was being updated with changes like this, but it seems to not be done anymore - this change has not bumbed the HIVE_CLI_SERVICE_PROTOCOL version when adding the new thrift messages.
What is currently used to ensure protocol compatibility?

> 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
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HIVE-18240.01.patch, 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
(v8.3.4#803005)