Return-Path: X-Original-To: apmail-hive-user-archive@www.apache.org Delivered-To: apmail-hive-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7573417FC6 for ; Wed, 9 Sep 2015 00:37:23 +0000 (UTC) Received: (qmail 97114 invoked by uid 500); 9 Sep 2015 00:37:21 -0000 Delivered-To: apmail-hive-user-archive@hive.apache.org Received: (qmail 97044 invoked by uid 500); 9 Sep 2015 00:37:21 -0000 Mailing-List: contact user-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hive.apache.org Delivered-To: mailing list user@hive.apache.org Received: (qmail 97034 invoked by uid 99); 9 Sep 2015 00:37:21 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Sep 2015 00:37:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 1555B18041A for ; Wed, 9 Sep 2015 00:37:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.879 X-Spam-Level: ** X-Spam-Status: No, score=2.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Gd-nn2x93ad8 for ; Wed, 9 Sep 2015 00:37:20 +0000 (UTC) Received: from mail-la0-f53.google.com (mail-la0-f53.google.com [209.85.215.53]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id DCF1243C67 for ; Wed, 9 Sep 2015 00:37:19 +0000 (UTC) Received: by laeb10 with SMTP id b10so81275899lae.1 for ; Tue, 08 Sep 2015 17:37:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ars9OWVqzRNt/8pQLcCNCD+wJEGDMOQSac0fOmPA5dU=; b=zo5rJ2CdZT4NN1qNEzA5GILeNuefDjvjZ0hkM/m+5zstwKofmoEx9A1muEy4WIOKHf 2HUlkSfkV1aMwmL67+fIUSYWydOR/j5n6OlNpEsjMmZfefZhXERdp4hk1m8K0qdcuX6e iPbn0YTT8VIsFiHvNj/4NZ0GbWMUz8sL45iGyrLoAMrPPqfP2oE0bSzqIJXXwNYvWmlB B2HJrRHNp5yb6eFox1YHaOLT27Ke3Y6/P6gMbon7Ka2QcDenLnOqhASzVAj5HF56V0sT kVXsKHTd/kYek9wlaxmdOBWWin+H1MEbY1o2H1CuJ5a28IjFY4+iQ3OmpBP5MWtWIKdz e1JQ== MIME-Version: 1.0 X-Received: by 10.112.181.197 with SMTP id dy5mr25832165lbc.109.1441759032840; Tue, 08 Sep 2015 17:37:12 -0700 (PDT) Received: by 10.25.42.208 with HTTP; Tue, 8 Sep 2015 17:37:12 -0700 (PDT) Date: Tue, 8 Sep 2015 20:37:12 -0400 Message-ID: Subject: Logging configuration From: Steve Howard To: "user@hive.apache.org" Content-Type: multipart/alternative; boundary=001a11c376a20115e6051f45afdb --001a11c376a20115e6051f45afdb Content-Type: text/plain; charset=UTF-8 We are having an issue for which we would like to enable logging. The component is org.apache.hadoop.hive.ql.exec.persistence.HybridHashTableContainer. We have added entries to both hive-log4.properties and hive-exec-log4j.properties as follows: log4j.appender.ts=org.apache.log4j.FileAppender log4j.appender.ts.file=/tmp/myhive.txt log4j.appender.ts.layout = org.apache.log4j.SimpleLayout log4j.logger.org.apache.hadoop.hive=INFO,ts We see the component mentioned above in the stack trace for the exception we are troubleshooting. However, we see nothing in either the hive log or our custom log appender. We have tried naming the entire component, changing INFO to DEBUG, etc. but no output for the LOG.info() line we see in the source code for the component (which is in the method that is part of the stack trace). We do see other INFO type messages in the log that we don't normally see. We did restart hiveserver2 prior to running the problematic query. How do you configure logging for a single component, or even package tree like org.apache.hadoop.hive --001a11c376a20115e6051f45afdb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
We are having an issue for which we would like to enable l= ogging.=C2=A0 The component is org.apache.hadoop.hive.ql.exec.persistence.H= ybridHashTableContainer.=C2=A0 We have added entries to both hive-log4.prop= erties and=C2=A0hive-exec-log4j.properties as follows:

<= div>log4j.appender.ts=3Dorg.apache.log4j.FileAppender
log4j.appen= der.ts.file=3D/tmp/myhive.txt
log4j.appender.ts.layout =3D org.ap= ache.log4j.SimpleLayout
log4j.logger.org.apache.hadoop.hive=3DINF= O,ts

We see the component mentioned abov= e in the stack trace for the exception we are troubleshooting.=C2=A0 Howeve= r, we see nothing in either the hive log or our custom log appender.
<= div>
We have tried naming the entire component, changing INFO= to DEBUG, etc. but no output for the LOG.info() line we see in the source = code for the component (which is in the method that is part of the stack tr= ace).=C2=A0 We do see other INFO type messages in the log that we don't= normally see.=C2=A0 We did restart hiveserver2 prior to running the proble= matic query.

How do you configure logging for a si= ngle component, or even package tree like org.apache.hadoop.hive
=
--001a11c376a20115e6051f45afdb--