You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2017/12/07 00:29:00 UTC

[jira] [Commented] (HIVE-18004) investigate deriving app name from JDBC connection for pool mapping

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

Sergey Shelukhin commented on HIVE-18004:
-----------------------------------------

Looking at Tableau connecting via ODBC, I cannot see any identifying information. The properties map Tableau/ODBC passes to HS2 is an empty map. It is possible that some information is  given to the ODBC driver, but not to HS2 via that...
However,
1) JDBC setClientInfo and getClientInfo are not implemented in Hive JDBC driver and that seems to work just fine, so I assume not many people use these; we might implement them anyway in case someone does and catches the exception.
2) Judging by e.g. https://help.sap.com/doc/52715f71adba4aaeb480d946c742d1f6/2.0.00/en-US/e90fa1f0e06e4840aa3ee2278afae16b.html it looks like other tools rely on JDBC url arguments for this stuff, not on JDBC (or ODBC) API. So, we might do the same.

cc [~hagleitn] [~cartershanklin]

> investigate deriving app name from JDBC connection for pool mapping
> -------------------------------------------------------------------
>
>                 Key: HIVE-18004
>                 URL: https://issues.apache.org/jira/browse/HIVE-18004
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>
> There are some client info fields that popular apps (Tableau, etc) might populate; this might allow us to map queries to pools based on an application used. Need to take a look (see the doc for an example API we might look into)



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