Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 25 Jan 2012 18:18:42 +0000 (UTC)
From: "Phabricator (Updated) (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: 
 <1794823543.77167.1327515522509.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <143946526.74531.1327445440095.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HIVE-2746) Metastore client doesn't log properly
 in case of connection failure to server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phabricator updated HIVE-2746:
------------------------------

    Attachment: HIVE-2746.D1395.2.patch

ashutoshc updated the revision "HIVE-2746 [jira] Metastore client doesn't log properly in case of connection failure to server".
Reviewers: JIRA, cwsteinbach

  Incorporated Carl's suggestions. Fixed indentation. Moved both setugi functionality as well as secure transport setup outside of for loop, since retrials are for transport.open() and that code doesn't belong in for loop.

REVISION DETAIL
  https://reviews.facebook.net/D1395

AFFECTED FILES
  metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStoreClient.java

                
> Metastore client doesn't log properly in case of connection failure to server
> -----------------------------------------------------------------------------
>
>                 Key: HIVE-2746
>                 URL: https://issues.apache.org/jira/browse/HIVE-2746
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.8.0
>            Reporter: Ashutosh Chauhan
>            Assignee: Ashutosh Chauhan
>         Attachments: HIVE-2746.D1395.1.patch, HIVE-2746.D1395.2.patch
>
>
> LOG.error(e.getStackTrace()) in current code prints memory location of StackTraceElement[] instead of message.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira