Return-Path: X-Original-To: apmail-hive-user-archive@www.apache.org Delivered-To: apmail-hive-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DE554D0A5 for ; Sat, 25 Aug 2012 12:30:31 +0000 (UTC) Received: (qmail 16385 invoked by uid 500); 25 Aug 2012 12:30:31 -0000 Delivered-To: apmail-hive-user-archive@hive.apache.org Received: (qmail 15580 invoked by uid 500); 25 Aug 2012 12:30:22 -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 15537 invoked by uid 99); 25 Aug 2012 12:30:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Aug 2012 12:30:21 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of alokawi@gmail.com designates 209.85.216.41 as permitted sender) Received: from [209.85.216.41] (HELO mail-qa0-f41.google.com) (209.85.216.41) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Aug 2012 12:30:14 +0000 Received: by qafk30 with SMTP id k30so1183032qaf.14 for ; Sat, 25 Aug 2012 05:29:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=5gENSosd6J0B64HUHKoU6xkYSYm816DqNeew0ZZGwqg=; b=AMowZqOCZtwRrracyVHye+2QzQpVCxzEgqygeHe5MiXNl0Wp8AzBTQZ7JIY498mwTw FVPvLiH9gKM88gW6kl/pXhSMfjpm/VoPm6ZwEhiSgH5xWha3lLRFf+CZ7ns2JNcefuJQ L6wJlrXY6xKR8lU6JjUt9lVDX+goI3/r4lJ+1xZS4+83Gbj1KT2Iuqu2ohFROLeMiG2a QiwRAGprP2T6w7Pbo9u+wfGjVv3bvcjgkX/C/wUFEttYYuQphHEAlgaf5jt31rUJuVSd xUfFaVwUZq0KLCvDpRH73F8Tx1JEfNK5zuH/mVmX8lFXxCnujM3TNuhoYrzhWs9Eo7KE VGFA== MIME-Version: 1.0 Received: by 10.229.135.83 with SMTP id m19mr3893239qct.78.1345897793787; Sat, 25 Aug 2012 05:29:53 -0700 (PDT) Received: by 10.49.27.8 with HTTP; Sat, 25 Aug 2012 05:29:53 -0700 (PDT) In-Reply-To: References: <2051305521-1345810255-cardhu_decombobulator_blackberry.rim.net-1556424874-@b25.c15.bise7.blackberry> Date: Sat, 25 Aug 2012 17:59:53 +0530 Message-ID: Subject: Re: alter external table location with new namenode address From: Alok Kumar To: user@hive.apache.org Content-Type: text/plain; charset=ISO-8859-1 Carl, I tried and found ALTER TABLE SET LOCATION command can't be used to set location for non-native tables. In my case, where all hive tables are mapped with tables in hbase, ALTER TABLE SET LOCATION was not possible!! I agree it wasn't a good idea though but only option i believe or is it available with any newer hive release? Thanks, Alok On Sat, Aug 25, 2012 at 1:22 AM, Carl Steinbach wrote: > Directly accessing the metastore schema is generally not a good idea. > Instead I recommend using the ALTER TABLE SET LOCATION command: > > https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-AlterTable%2FPartitionLocation > > Thanks. > > Carl > > On Fri, Aug 24, 2012 at 10:56 AM, Alok Kumar wrote: >> >> Bejoy, >> >> Thank you for your help. >> updated metastore n its working fine. >> >> Regards >> -Alok >> >> On Fri, Aug 24, 2012 at 5:40 PM, Bejoy KS wrote: >> > Yes you need to update the metastore db directly for this to be in >> > effect. >> > >> > Regards >> > Bejoy KS >> > >> > Sent from handheld, please excuse typos. >> > >> > -----Original Message----- >> > From: Alok Kumar >> > Date: Fri, 24 Aug 2012 13:30:36 >> > To: ; >> > Reply-To: user@hive.apache.org >> > Subject: alter external table location with new namenode address >> > >> > Hello, >> > >> > We have hive external table mapped to hbase, now moving >> > from pseudo distributed to fully distributed hadoop cluster. >> > >> > found that hive queries are still pointing to older namenode address >> > ie: hdfs://localhost:9000/user/hive/warehouse/ as it stores >> > full uri in its derby metastore. >> > >> > Q . what would be the best way to set new namenode address? >> > >> > Alter table command on hive shell to set hdfs location is only >> > possible for native tables!! >> > should i update derby "DB_LOCATION_URI" column directly? >> > >> > Your help/suggestion is highly appreciated >> > >> > Thanks, >> > Alok >> > >> > > > -- Alok Kumar