[jira] [Commented] (KUDU-3189) kudu hms fix should log Hive Metatore URI

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on KUDU-3189:
-------------------------------------------------------

Commit 960e30055b12870ad425e746b907b9b7d9459194 in kudu's branch refs/heads/master from Zoltan Chovan
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=960e300 ]

KUDU-3189: log Hive Metatore URI when connecting

When 'kudu hms' is connecting to an HMS instance there is no user facing
information log about which HMS instance the connection is opened for.
This change adds a simple log line to the thrift client that shows this
information, but only when the verbosity level is set to 1.

Change-Id: Ide920bc1fca44e318d3c4e2921eb0588a82b7400
Reviewed-on: http://gerrit.cloudera.org:8080/17695
Tested-by: Kudu Jenkins
Reviewed-by: Attila Bukor <ab...@apache.org>


> kudu hms fix should log Hive Metatore URI
> -----------------------------------------
>
>                 Key: KUDU-3189
>                 URL: https://issues.apache.org/jira/browse/KUDU-3189
>             Project: Kudu
>          Issue Type: Improvement
>          Components: hms
>            Reporter: David Mollitor
>            Assignee: Zoltan Chovan
>            Priority: Minor
>
> https://kudu.apache.org/docs/command_line_tools_reference.html#hms-fix
> There is an optional parameter called {{hive_metastore_uris}}.  I recently hit a {{THRIFT_EAGAIN (timed out)}}  error but the kudu tool does not tell me which URI it is trying to connect to, which is confusing since I did not specify one.
> Please add a logging message that indicates which HMS it is connecting to.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)