Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 48C201060B for ; Wed, 24 Jul 2013 06:31:58 +0000 (UTC) Received: (qmail 63428 invoked by uid 500); 24 Jul 2013 06:31:56 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 63379 invoked by uid 500); 24 Jul 2013 06:31:55 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 63309 invoked by uid 500); 24 Jul 2013 06:31:52 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 63293 invoked by uid 99); 24 Jul 2013 06:31:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jul 2013 06:31:51 +0000 Date: Wed, 24 Jul 2013 06:31:51 +0000 (UTC) From: "Navis (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HIVE-4924) Support query timeout for jdbc2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navis updated HIVE-4924: ------------------------ Status: Patch Available (was: Open) > Support query timeout for jdbc2 > ------------------------------- > > Key: HIVE-4924 > URL: https://issues.apache.org/jira/browse/HIVE-4924 > Project: Hive > Issue Type: Improvement > Components: HiveServer2, JDBC > Reporter: Navis > Assignee: Navis > Priority: Trivial > Attachments: HIVE-4924.D11787.1.patch > > > support > {code} > Statement.setQueryTimeout(int timeout) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira