You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Deepesh Khandelwal (JIRA)" <ji...@apache.org> on 2015/03/13 23:42:38 UTC

[jira] [Created] (HIVE-9963) HiveServer2 deregister command doesn't provide any feedback

Deepesh Khandelwal created HIVE-9963:
----------------------------------------

             Summary: HiveServer2 deregister command doesn't provide any feedback
                 Key: HIVE-9963
                 URL: https://issues.apache.org/jira/browse/HIVE-9963
             Project: Hive
          Issue Type: Bug
          Components: HiveServer2
    Affects Versions: 0.14.0
            Reporter: Deepesh Khandelwal


HiveServer2 deregister functionality provided by HIVE-8288 doesn't provide any feedback upon completion. Here is a sample console output:
{noformat}
$ hive --service hiveserver2 --deregister 0.14.0-SNAPSHOT
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/root/hadoop/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/root/hive/lib/hive-jdbc-0.14.0-SNAPSHOT-standalone.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
{noformat}
This will not change even if the znode did not exist. Ideally we should print some feedback after the command completes like "HiveServer2 with version '0.14.0-SNAPSHOT' deregistered successfully" or in case of failure an appropriate reason "No HiveServer2 with version '0.14.0-SNAPSHOT' exists to deregister".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)