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 569C718847 for ; Tue, 20 Oct 2015 03:56:11 +0000 (UTC) Received: (qmail 81136 invoked by uid 500); 20 Oct 2015 03:56:09 -0000 Delivered-To: apmail-hive-user-archive@hive.apache.org Received: (qmail 81042 invoked by uid 500); 20 Oct 2015 03:56:09 -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 81032 invoked by uid 99); 20 Oct 2015 03:56:08 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Oct 2015 03:56:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 73EBAC0EC7 for ; Tue, 20 Oct 2015 03:56:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.908 X-Spam-Level: *** X-Spam-Status: No, score=3.908 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_REPLY=1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id ydWIPkL-trU6 for ; Tue, 20 Oct 2015 03:56:07 +0000 (UTC) Received: from mail-qg0-f51.google.com (mail-qg0-f51.google.com [209.85.192.51]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id B1B7220751 for ; Tue, 20 Oct 2015 03:56:06 +0000 (UTC) Received: by qgad10 with SMTP id d10so4627186qga.3 for ; Mon, 19 Oct 2015 20:56:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=ZKZg9YD/2ezguoUWSKYGqLg15hJ1kNmYEkcwOPy8Y/A=; b=OfHxEbQY3Pf56+jM2Fl+SrqUlknpffV4zgrVdLq0TagE3o0pJI2NMg1zG6xp8PK2hu ZW7AMW7ehvp9BLBdtf54+oCrtRBmWxBOXMRd81/7RtFx1gwDuKCYoH1o239bM3pZeN2K x6Zm3bJZYS2eK528+DAmpp316sCTRUzN1rRZFcEuVWoMqq0hTQuox06BHE0oIDyrLwdt WB7TgXTa1uhWXxSpsDrisziDJcBBLzrnJ6icUHEs3L96kZwpxJslpCE0snubV4QMGfk9 IRWImM7E+Lq8DLeCNdMynxWM+O29lI1txirbuVRvdbfuFbEvtfGkfXL7salUPQI3L9vt n12A== X-Received: by 10.140.101.168 with SMTP id u37mr1058117qge.103.1445313365795; Mon, 19 Oct 2015 20:56:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.111.66 with HTTP; Mon, 19 Oct 2015 20:55:46 -0700 (PDT) In-Reply-To: <201510200949309063380@163.com> References: <201510200949309063380@163.com> From: Jerrick Hoang Date: Mon, 19 Oct 2015 20:55:46 -0700 Message-ID: Subject: Re: Hiveserver2 client stdout To: user@hive.apache.org Content-Type: multipart/alternative; boundary=001a11c16fe0c1ebdf0522813d99 --001a11c16fe0c1ebdf0522813d99 Content-Type: text/plain; charset=UTF-8 That would just increase the log level on the server side right? I want the stdout log sent to the jdbc client. On Mon, Oct 19, 2015 at 6:49 PM, r7raul1984@163.com wrote: > start hiveserver2 with --hiveconf hive.root.logger=DEBUG,console . > Then check hiveserver2 log. > > ------------------------------ > r7raul1984@163.com > > > *From:* Jerrick Hoang > *Date:* 2015-10-20 09:03 > *To:* user > *Subject:* Hiveserver2 client stdout > Hi all, > > > I have a hiveserver2 client running on a remote server. I'm able to > connect to it via beeline CLI and everything works fine but when I try to > query via a JDBC client, the stdout is not there. For example, if the > server side throws an exception, beeline can show the exception but all the > JDBC client can do is giving me ` Error while processing statement: FAILED: > Execution Error, return code 2 from > org.apache.hadoop.hive.ql.exec.mr.MapRedTask` which is not very helpful. Is > there a way to capture all stdout stderr using a JDBC? I figure if beeline > is able to do it then I should be able to write a jdbc client to do it too, > > THanks, > J > > --001a11c16fe0c1ebdf0522813d99 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That would just increase the log level on the server side = right? I want the stdout log sent to the jdbc client.

On Mon, Oct 19, 2015 at 6:49 PM, = r7raul1984@163.com <r7raul1984@= 163.com> wrote:
start hiveserver2 with =C2=A0--hiveconf hive.root.logger=3D= DEBUG,console =C2=A0 =C2=A0. Then check hiveserver2 log.

=C2=A0
From:=C2=A0Jerrick Hoang
Date:= =C2=A02015-10-20=C2=A009:03
To:=C2=A0user
Subject:=C2= =A0Hiveserver2 client stdout
<= div>
Hi all,


I have a hiv= eserver2 client running on a remote server. I'm able to connect to it v= ia beeline CLI and everything works fine but when I try to query via a JDBC= client, the stdout is not there. For example, if the server side throws an= exception, beeline can show the exception but all the JDBC client can do i= s giving me `=C2=A0Error while processing statement: FAILED: Execution Erro= r, return code 2 from org.apache.hadoop.hive.ql.exec.mr.MapRedTask` which i= s not very helpful. Is there a way to capture all stdout stderr using a JDB= C? I figure if beeline is able to do it then I should be able to write a jd= bc client to do it too,

THanks,
J=C2=A0<= /div>

--001a11c16fe0c1ebdf0522813d99--