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 <alok...@gmail.com> 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 <bejoy...@yahoo.com> 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 <alok...@gmail.com> > > Date: Fri, 24 Aug 2012 13:30:36 > > To: <user@hbase.apache.org>; <u...@hive.apache.org> > > Reply-To: u...@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/<table-name> 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 > > > > >
