[HIVE-18240] support getClientInfo/setClientInfo in JDBC

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Assignee: Sergey Shelukhin
• Reporter: Sergey Shelukhin
• Created: 07/Dec/17 03:20
• Updated: 25/Oct/19 15:00
• Resolved: 12/Dec/17 01:43

Description

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.

Issue Links

• relates to: HIVE-18004 investigate deriving app name from JDBC connection for pool mapping
• links to: RB