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 568DD200B85 for ; Thu, 1 Sep 2016 07:24:26 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 31B1F160AB5; Thu, 1 Sep 2016 05:24:26 +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 757E5160AB4 for ; Thu, 1 Sep 2016 07:24:25 +0200 (CEST) Received: (qmail 73790 invoked by uid 500); 1 Sep 2016 05:24:24 -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 73780 invoked by uid 99); 1 Sep 2016 05:24:23 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2016 05:24:23 +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 6FC65186F6A for ; Thu, 1 Sep 2016 05:24:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id reOYmZlBRqjM for ; Thu, 1 Sep 2016 05:24:21 +0000 (UTC) Received: from mail-yw0-f172.google.com (mail-yw0-f172.google.com [209.85.161.172]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 289375FC0E for ; Thu, 1 Sep 2016 05:24:21 +0000 (UTC) Received: by mail-yw0-f172.google.com with SMTP id d130so16171127ywc.3 for ; Wed, 31 Aug 2016 22:24:21 -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; bh=kMp5xyVjV+MeQCY4BT75Aigc35T3MfeH6+NuJtVUYpI=; b=w7lBsb7o7NRBptdY0DQX+QEDWjJyw4ucI9VdzAL5ingT09Xx+1YdpNWiJ9wRbZylit IBiDmNa4g+ifQR7ILH5Ew/ZK751c85CfnQZgr4jMg3MXU93RFl9AupKq3tk3YHJXKeAI z8/HC5uXK85CuXCShTf3ywZqJ4Jyi03tkv8rc2Ceea77jfvSo8pyCmBWtmma83G+OdPw FC9LQQWpDKdCd2j/I5bqJQxv5kVVKk2x4Wschn/wqrApGaDL+C+7vI/qQFgUk7O8SwZQ XvoMeDT64uakpW0Hfe62oDVzMlervLi0rvkNrNAheHWk60UsT/aOemFbH77lf/C+ICZM cklA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=kMp5xyVjV+MeQCY4BT75Aigc35T3MfeH6+NuJtVUYpI=; b=atOokz8kfMu0AZhlUtOYFnzviJTLvEEVThqfpISxU+3E2z6eDdhvttxFb6NpfYMNnV xY/n5VxApR2LMQmlSXgYUO0McUCc+3hsXPEKyacYE3uzqvPg4rMMyk0ZIwptSC+FNnvN WQlgY+zApcHLQYka/mUOfKetT1EbOOjy+AKKIrtWZPSqRfs3qF+sRAwHKfHkVsZczrrI LxXfypxhoxqR77mm/q6bB53WNqDrRmYRM5pNSD+m7eKjQ6snWzWm7b8Z5a3ESjGr7UJ4 KGSwnzfOR363XI6pE0s/f39vxvg9dLJK7XWdCwnLRcnJmm/4RRMizgA71d3NiqY0ihU2 /dzQ== X-Gm-Message-State: AE9vXwO9b+TH6xpqaP21pu2R/RpaWgEw+m2pfMVqjP0r9KaC3LgMW67R8TQglwGugQR+o2ZwE+rR/Y+sP/SIVw== X-Received: by 10.129.70.137 with SMTP id t131mr12052159ywa.268.1472707460626; Wed, 31 Aug 2016 22:24:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.165.131 with HTTP; Wed, 31 Aug 2016 22:24:20 -0700 (PDT) In-Reply-To: References: From: ravi teja Date: Thu, 1 Sep 2016 10:54:20 +0530 Message-ID: Subject: Re: Quota for rogue ad-hoc queries To: user@hive.apache.org Content-Type: multipart/alternative; boundary=001a114c89660c7ef9053b6b6d92 archived-at: Thu, 01 Sep 2016 05:24:26 -0000 --001a114c89660c7ef9053b6b6d92 Content-Type: text/plain; charset=UTF-8 Thanks Mich, Unfortunately we have many insert queries. Are there any other ways? Thanks, Ravi On Wed, Aug 31, 2016 at 9:45 PM, Mich Talebzadeh wrote: > Trt this > > hive.limit.optimize.fetch.max > > - Default Value: 50000 > - Added In: Hive 0.8.0 > > Maximum number of rows allowed for a smaller subset of data for simple > LIMIT, if it is a fetch query. Insert queries are not restricted by this > limit. > > > HTH > > Dr Mich Talebzadeh > > > > LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw > * > > > > http://talebzadehmich.wordpress.com > > > *Disclaimer:* Use it at your own risk. Any and all responsibility for any > loss, damage or destruction of data or any other property which may arise > from relying on this email's technical content is explicitly disclaimed. > The author will in no case be liable for any monetary damages arising from > such loss, damage or destruction. > > > > On 31 August 2016 at 13:42, ravi teja wrote: > >> Hi Community, >> >> Many users run adhoc hive queries on our platform. >> Some rogue queries managed to fill up the hdfs space and causing >> mainstream queries to fail. >> >> We wanted to limit the data generated by these adhoc queries. >> We are aware of strict param which limits the data being scanned, but it >> is of less help as huge number of user tables aren't partitioned. >> >> Is there a way we can limit the data generated from hive per query, like >> a hve parameter for setting HDFS quotas for job level *scratch* >> directory or any other approach? >> What's the general approach to gaurdrail such multi-tenant cases. >> >> Thanks in advance, >> Ravi >> > > --001a114c89660c7ef9053b6b6d92 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks Mich,

Unfortunately we have many= insert queries.
Are there any other ways?

Thanks,
Ravi

On Wed, Aug 31, 2016 at 9:45 PM, Mich Talebzadeh <mich.talebzadeh@gmail.com> wrote:
Trt this

hive.limi= t.optimize.fetch.max
  • <= font color=3D"#0000ff">Default Value:=C2= =A050000
  • Added In: Hive 0.8.0

M= aximum number of rows allowed for a smaller subset of data for= simple LIMIT, if it is a fetch query. Insert queries are not restricted by= this limit.


=
HTH

Dr Mich Talebzadeh

=C2=A0

LinkedIn =C2=A0https://www.linkedin.com/profile/view?id= =3DAAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw

=C2=A0

http:= //talebzadehmich.wordpress.com


Disclaimer:=C2=A0= Use it=C2=A0at your own risk. Any and all responsib= ility for any loss, damage or destruction of data or any other property which may arise from relying on this email= 9;s=C2=A0technical=C2=A0content is explicitly disclaimed. The author will in no case be liable for any monetary damages arising from = such loss, damage or destruction.

=C2=A0

<= font color=3D"#000000" face=3D"Times New Roman" size=3D"3">

On 31 August 2016 at 13:42, ravi teja <r= aviorteja@gmail.com> wrote:
Hi Community,

Many users run adhoc hive queries on o= ur platform.
Some rogue queries managed to fill up the hdfs space= and causing mainstream queries to fail.

We wanted= to limit the data generated by these adhoc queries.
We are aware= of strict param which limits the data being scanned, but it is of less hel= p as huge number of user tables aren't partitioned.

Is there a way we can limit the data generated from hive per query, l= ike a hve parameter for setting HDFS quotas for job level=C2=A0scratch directory or any other approach?
What's the general approa= ch to gaurdrail such multi-tenant cases.

Thanks in= advance,
Ravi


--001a114c89660c7ef9053b6b6d92--