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 109E5200CAE for ; Wed, 21 Jun 2017 16:32:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0F378160BD0; Wed, 21 Jun 2017 14:32:07 +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 54D42160BE2 for ; Wed, 21 Jun 2017 16:32:06 +0200 (CEST) Received: (qmail 9559 invoked by uid 500); 21 Jun 2017 14:32:05 -0000 Mailing-List: contact issues-help@impala.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@impala.incubator.apache.org Delivered-To: mailing list issues@impala.incubator.apache.org Received: (qmail 9467 invoked by uid 99); 21 Jun 2017 14:32:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jun 2017 14:32:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id C8BC51A0230 for ; Wed, 21 Jun 2017 14:32:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 10S919bWDPUT for ; Wed, 21 Jun 2017 14:32:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4ACB360EC3 for ; Wed, 21 Jun 2017 14:32:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 86D08E0D4D for ; Wed, 21 Jun 2017 14:32:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 13F7421943 for ; Wed, 21 Jun 2017 14:32:00 +0000 (UTC) Date: Wed, 21 Jun 2017 14:32:00 +0000 (UTC) From: "Ninad Shringarpure (JIRA)" To: issues@impala.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IMPALA-5550) Session level SET LIMIT in ODBC/JDBC connections MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 21 Jun 2017 14:32:07 -0000 Ninad Shringarpure created IMPALA-5550: ------------------------------------------ Summary: Session level SET LIMIT in ODBC/JDBC connections Key: IMPALA-5550 URL: https://issues.apache.org/jira/browse/IMPALA-5550 Project: IMPALA Issue Type: Improvement Components: Clients Reporter: Ninad Shringarpure Priority: Minor When using Impala in user dashboards like Tableau, users have an ability to write custom queries. In some cases when users due to lack of knowledge or understanding write bad queries returning, in some cases, billions of rows there has to be an ability to safeguard against this. A session level setting in ODBC connection provided like SET LIMIT=100000 get help limit such issues and accidental resource consumption in the cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)