Return-Path: 
 <dev-return-26662-apmail-hive-dev-archive=hive.apache.org@hive.apache.org>
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 741519C24
	for <apmail-hive-dev-archive@www.apache.org>;
 Wed,  5 Oct 2011 12:38:56 +0000 (UTC)
Received: (qmail 36157 invoked by uid 500); 5 Oct 2011 12:38:56 -0000
Delivered-To: apmail-hive-dev-archive@hive.apache.org
Received: (qmail 36115 invoked by uid 500); 5 Oct 2011 12:38:56 -0000
Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@hive.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@hive.apache.org>
List-Post: <mailto:dev@hive.apache.org>
List-Id: <dev.hive.apache.org>
Reply-To: dev@hive.apache.org
Delivered-To: mailing list dev@hive.apache.org
Received: (qmail 36107 invoked by uid 500); 5 Oct 2011 12:38:56 -0000
Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org
Received: (qmail 36102 invoked by uid 99); 5 Oct 2011 12:38:56 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Oct 2011 12:38:56 +0000
X-ASF-Spam-Status: No, hits=-2000.5 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Oct 2011 12:38:55 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 74E3C2AA30D
	for <hive-dev@hadoop.apache.org>; Wed,  5 Oct 2011 12:38:34 +0000 (UTC)
Date: Wed, 5 Oct 2011 12:38:34 +0000 (UTC)
From: "kalyan ram (Commented) (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: 
 <841773251.11489.1317818314480.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <952253988.7789.1317739714188.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HIVE-2478) Support dry run option in hive
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-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120890#comment-13120890 ] 

kalyan ram commented on HIVE-2478:
----------------------------------

Yes we can use EXPLAIN as well. In MySql older versions for some queries having sub queries <explain> was executing the sub queries so I was thinking on those terms. So in Hive is it that we never execute the query if EXPLAIN is present ? This feature might still be useful in remote cases where you can't go and change your queries. For example if you want to check if your queries will work against a new version of hive we can set this property and check without modifying the query.
                
> Support dry run option in hive
> ------------------------------
>
>                 Key: HIVE-2478
>                 URL: https://issues.apache.org/jira/browse/HIVE-2478
>             Project: Hive
>          Issue Type: Improvement
>          Components: Configuration
>    Affects Versions: 0.9.0
>            Reporter: kalyan ram
>            Priority: Minor
>         Attachments: HIVE-2478-1.patch
>
>
> Hive currently doesn't support a dry run option. For some complex queries we just want to verify the query syntax initally before running it. A dry run option where just the parsing is done without actual execution is a good option.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira