Return-Path: Delivered-To: apmail-hive-user-archive@www.apache.org Received: (qmail 31646 invoked from network); 8 Feb 2011 00:30:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Feb 2011 00:30:54 -0000 Received: (qmail 73992 invoked by uid 500); 8 Feb 2011 00:30:53 -0000 Delivered-To: apmail-hive-user-archive@hive.apache.org Received: (qmail 73694 invoked by uid 500); 8 Feb 2011 00:30:53 -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 73582 invoked by uid 99); 8 Feb 2011 00:30:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Feb 2011 00:30:53 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of edlinuxguru@gmail.com designates 209.85.161.48 as permitted sender) Received: from [209.85.161.48] (HELO mail-fx0-f48.google.com) (209.85.161.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Feb 2011 00:30:46 +0000 Received: by fxm2 with SMTP id 2so5714055fxm.35 for ; Mon, 07 Feb 2011 16:30:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ZNUQKet8YrhpY/M4lsycSK50nFB3n30+Ax4NCjzMXHQ=; b=E4b/Fc10RBSz6/mpteBk4V6Rd+ciiCx61lXGZ4/ziqB0Bb5lD2rJQEGQ1WMWAnEYtC c2ZVI+NtR8Ge+lBaiaO+ib9L8kAmgQFUoJEEVToQSb21R+T86ZPXNU6Jm5W2hWvtWxi5 U85lrzdaDzOdnB0fwaE4FQ6IsyOi4j2wZPNG8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=EwbeuuDBkDy6A98pSvwtSSXn2/7TBaMrfkaZTSYmCdXCuqOE0M8W8AFRBspWxoddfk PQbXIszUQONVJ08qao/WJPI6o9YEomjRAaw2Oe9cTFg0ssL62igk+IVt1JBvTLLrRIlx khUAtjn4wjnd9punFvhR49oVku+1ffoVDPmTA= MIME-Version: 1.0 Received: by 10.223.114.14 with SMTP id c14mr735543faq.103.1297125025742; Mon, 07 Feb 2011 16:30:25 -0800 (PST) Received: by 10.223.115.12 with HTTP; Mon, 7 Feb 2011 16:30:25 -0800 (PST) In-Reply-To: References: Date: Mon, 7 Feb 2011 19:30:25 -0500 Message-ID: Subject: Re: Safe to upgrade to Hive 0.7.0? From: Edward Capriolo To: user@hive.apache.org Cc: "" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Feb 7, 2011 at 7:27 PM, Gokul Pillai wrote: > I have a Hadoop 0.20 cluster with Hive 0.6. > I want to try out the ngrams functions in 0.7 (trunk) and so want to > upgrade. > What would you recommend. Can I have a Hive 0.7 install in a different > location (for trial) and point it to the same cluster. > If not, is there an upgrade utility? > I am not concerned about existing tables. I just want to make sure I can = run > Hive 0.6 and Hive 0.7 side by side. > Regards > Gokul > > On Wed, Dec 8, 2010 at 9:26 AM, Edward Capriolo > wrote: >> >> On Wed, Dec 8, 2010 at 12:06 PM, Ning Zhang wrote: >> > These are datanucleus paramesters found in >> > hive-default.xml/hive-site.xml. If you change them to the following th= e >> > metastore schema won't be changed automatically (may be good for preve= nting >> > accidents). >> > >> > >> > >> > =A0datanucleus.autoCreateSchema >> > =A0false >> > >> > >> > >> > =A0datanucleus.fixedDatastore >> > =A0true >> > >> > >> > >> > ________________________________________ >> > From: Edward Capriolo [edlinuxguru@gmail.com] >> > Sent: Wednesday, December 08, 2010 7:19 AM >> > To: user@hive.apache.org >> > Cc: >> > Subject: Re: Safe to upgrade to Hive 0.7.0? >> > >> > On Wed, Dec 8, 2010 at 9:55 AM, Ryan LeCompte >> > wrote: >> >> Hey guys, >> >> We would like to experiment with some of the features in the current >> >> trunk >> >> (0.7) release. Do you think at this point it's nearing >> >> "production-ready" ? >> >> Are there any metastore migration scripts or anything like that befor= e >> >> upgrading to 0.7 from 0.6? >> >> Thanks, >> >> Ryan >> >> >> > >> > Ryan, >> > >> > This is hard to say. There are many changes going in around indexing >> > and authorization. IMHO everyone is taking a lot of care in the design >> > however, it is still subject to change. >> > >> > If i were compelled to update I would spin up a new instance into a >> > new meta-store back end. Then compare the schema of current with 0.6.X >> > like a diff of 'show create tables'. >> > >> > Just an FYI. I applied two different hive trunks between 0.5 and 0.6. >> > and I never needed the update scripts because hive happily updated the >> > schema for me. After my final upgrade to 0.7.0 I re-ran everything in >> > the upgrade script just to be safe. Nothing noticeably bad happened to >> > me during the duration. >> > >> > I suspect many people will not need to run the update scripts since in >> > the stock configuration hive seems to auto-update anyway. (Someone >> > correct me if I am wrong here.) Does anyone know how to specifically >> > which variable controls this? >> > >> > Edward >> > >> >> https://issues.apache.org/jira/browse/HIVE-1841 -- please comment > > I would not do it. The new version will attempt to update the meta-store. I would just attempt to build n grams udf into a separate JAR and load it up with create temporary function.