Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4F73B200D68 for ; Thu, 14 Dec 2017 06:42:45 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4DD46160C24; Thu, 14 Dec 2017 05:42:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6C23A160C23 for ; Thu, 14 Dec 2017 06:42:44 +0100 (CET) Received: (qmail 23847 invoked by uid 500); 14 Dec 2017 05:42:43 -0000 Mailing-List: contact user-help@impala.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@impala.apache.org Delivered-To: mailing list user@impala.apache.org Received: (qmail 23837 invoked by uid 99); 14 Dec 2017 05:42:43 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Dec 2017 05:42:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id ECF82C3AFB for ; Thu, 14 Dec 2017 05:42:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=cloudera.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id POkp6AoudG1f for ; Thu, 14 Dec 2017 05:42:40 +0000 (UTC) Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 141545F20B for ; Thu, 14 Dec 2017 05:42:40 +0000 (UTC) Received: by mail-oi0-f41.google.com with SMTP id t81so3165293oih.13 for ; Wed, 13 Dec 2017 21:42:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudera.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=BH/xRf3DDSdhqUfJ5mt8WExq9YVIx8aNsL9+N9CbH8s=; b=HcXxjZl6yzI4MKkcc2nyCdbSQXWfOcKbuPuWw2D/T3fhmzElM2hnIDKA5PMtMJtwht aDNUnZ88xkoCr50dZ7WhSsy+eOiswL9uZWyGzxlIVliE7pCcCbZK1rXRoJ/kAt2lG2uj i5VHgo4rcPZAkD0m1W3cBhCeXxUhPwbCaazU8zQ0xTWOemPOQs6KG5IKIaYavaQnqDB2 yRWhhAEmdhcLzYwmKFfHvXgP7j5KL/QJbR3ShQ7JyQziGb8DwhEZYBMgkw6seuPGLi7V vXiJelqbZO36mr0ibX9JAVYT5Q96kYbHbKWiQTEfXcW14DTTG3iNcWVb2CtZmMQ1zdny vs4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=BH/xRf3DDSdhqUfJ5mt8WExq9YVIx8aNsL9+N9CbH8s=; b=csanzEP5YhZwTRLKBQ/orIMmAaUeVBThkMQBAvnSK7zCsyytEFhof7itfaBq3uxIjF llyYN87outsjTTxB/p3S7eyLcCuemjkh7wvTetLWLDlTKOgErkGSgzgEmRRwBFhdwhQd tDUn152YsKAEZBUbrWkyz79WR1sWLEJaS6PauXnPSxGW+oOYU+xWkZyZ7Y5f5/oD+XMy cHmsie0lRLzQtT1BOgF/S887IMgUPelPDeevhXyXr8dXA9+t5h41L1iZKFNYDw/U6cVq xLBXvBj8rxN3dNJTS1Tv+EVWnMFM3XFlK5dFpUNJprE5GOAN6K7PdDgRyJ5IdwZYGpPH c08A== X-Gm-Message-State: AKGB3mLvB0mnyhoBjg5cqFS88X2U0NG7NTyx7Zl15ibmmhw7qyguQoxG fXi1vRsquERfmSd2IZXoBiSA64XlC/19Y6tgIhaP0g== X-Google-Smtp-Source: ACJfBouLUvrGoonFRyvxjCSTTdgznNtQG9uf97ki9WeqabjMZg6lF21vgwnyxWMXmKA1Fx5405cjEFDw5uIKOp8zTxk= X-Received: by 10.202.199.134 with SMTP id x128mr3709459oif.63.1513230158571; Wed, 13 Dec 2017 21:42:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.202.235.65 with HTTP; Wed, 13 Dec 2017 21:42:38 -0800 (PST) In-Reply-To: References: From: Alexander Behm Date: Wed, 13 Dec 2017 21:42:38 -0800 Message-ID: Subject: Re: Using comments in query for detailed monitoring To: user@impala.apache.org Content-Type: multipart/alternative; boundary="001a11c17e4a10d7bb0560465a8d" archived-at: Thu, 14 Dec 2017 05:42:45 -0000 --001a11c17e4a10d7bb0560465a8d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Not sure if this will work, but you could try enabling useNativeQuery in the driver. Theoretically that should send the query string including comments verbatim to Impala. On Wed, Dec 13, 2017 at 7:57 PM, Philip Zeyliger wrote: > I=E2=80=99m a little surprised comments are being stripped, but adding (1= =3D1 or > =E2=80=9C=E2=80=9D=3D=E2=80=9Cyour comment=E2=80=9D) to a where clause wo= uld work similarly. Impala will > simplify that away during query compilation. > > P > > On Wed, Dec 13, 2017 at 7:22 PM Sunil Parmar > wrote: > >> Server version: impalad version 2.9.0-cdh5.12.1 RELEASE (build >> 5131a031f4aa38c1e50c430373c55ca53e0517b9) >> >> One of the primary use of of Impala is it acts as a backend to a web >> application exposed to lot of users. We are trying to build monitoring >> metrics per web page, logged in user and other things that are not >> typically supplied in the query string. We were thinking to use query >> comments to pass such information along with query. It worked fine when >> query is executed using impala-shell; I can see the comments in the impa= la >> monitoring page i.e. on port #25000 but when comments are sent over JDBC= ; >> they're not visible to Impalad. >> >> 1. Is there an configuration in Impala driver ? We're using >> >> com.cloudera.impala >> impala-jdbc >> 2.5.30 >> compile >> >> >> 2. Is there any other way to send such hints along with query ? >> >> >> Thanks, >> Sunil >> >> --001a11c17e4a10d7bb0560465a8d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Not sure if this will work, but you could try enabling use= NativeQuery in the driver. Theoretically that should send the query string = including comments verbatim to Impala.

=
On Wed, Dec 13, 2017 at 7:57 PM, Philip Zeyliger= <philip@cloudera.com> wrote:
I=E2=80=99m a little surprised comments are be= ing stripped, but adding (1=3D1 or =E2=80=9C=E2=80=9D=3D=E2=80=9Cyour comme= nt=E2=80=9D) to a where clause would work similarly. Impala will simplify t= hat away during query compilation.=C2=A0

P

On Wed= , Dec 13, 2017 at 7:22 PM Sunil Parmar <sunilosunil@gmail.com> wrote:
Server version: impalad version 2.9.= 0-cdh5.12.1 RELEASE (build 5131a031f4aa38c1e50c430373c55ca53e0517b9)

One of the primary use of of Impala is it acts as a= backend to a web application exposed to lot of users. We are trying to bui= ld monitoring metrics per web page, logged in user and other things that ar= e not typically supplied in the query string. We were thinking to use query= comments to pass such information along with query. It worked fine when qu= ery is executed using impala-shell; I can see the comments in the impala mo= nitoring page i.e. on port #25000 but when comments are sent over JDBC ; th= ey're not visible to Impalad.

1. Is there= an configuration in Impala driver ? We're using
=C2=A0 = =C2=A0=C2=A0 <dependency>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <group= Id>com.cloudera.impala</groupId>
=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 <artifactId>impala-jdbc</artifactId>
=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 <version>2.5.30</version>
=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 <scope>compile</scope>
=C2=A0=C2=A0=C2=A0= </dependency>

2. Is there any other way= to send such hints along with query ?


<= div>Thanks,
Sunil


--001a11c17e4a10d7bb0560465a8d--