Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 10 Mar 2011 00:02:59 +0000 (UTC)
From: "Joydeep Sen Sarma (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: 
 <1785814054.9605.1299715379498.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <123619940.9551.1299713579426.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Reopened: (HIVE-2039) remove hadoop version check from hive
 cli shell script
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joydeep Sen Sarma reopened HIVE-2039:
-------------------------------------

      Assignee: Joydeep Sen Sarma

spoke too fast - the version check has moved to a different place - but it's still there. i plan to provide a way to avoid the version check (via env var) because it's pretty expensive. it would still be there by default.

> remove hadoop version check from hive cli shell script
> ------------------------------------------------------
>
>                 Key: HIVE-2039
>                 URL: https://issues.apache.org/jira/browse/HIVE-2039
>             Project: Hive
>          Issue Type: Improvement
>          Components: CLI
>            Reporter: Joydeep Sen Sarma
>            Assignee: Joydeep Sen Sarma
>
> looking at cli startup times - one thing i noticed is that the version check in execHiveCmd.sh consumes 0.5-1s of wall-clock time (depending on where hive is installed).
> AFAIK - hive doesn't support versions less than 20 right now - and this check is only to check if version is less than 20. So we should be able to safely take it out. please comment if that is not the case.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira