Alok Kumar 2012-08-24, 08:00
Bejoy KS 2012-08-24, 12:10
Alok Kumar 2012-08-24, 17:56
-Re: alter external table location with new namenode address
Carl Steinbach 2012-08-24, 19:52
Directly accessing the metastore schema is generally not a good idea.
Instead I recommend using the ALTER TABLE SET LOCATION command:
On Fri, Aug 24, 2012 at 10:56 AM, Alok Kumar <[EMAIL PROTECTED]> wrote:
> Thank you for your help.
> updated metastore n its working fine.
> On Fri, Aug 24, 2012 at 5:40 PM, Bejoy KS <[EMAIL PROTECTED]> wrote:
> > Yes you need to update the metastore db directly for this to be in
> > Regards
> > Bejoy KS
> > Sent from handheld, please excuse typos.
> > -----Original Message-----
> > From: Alok Kumar <[EMAIL PROTECTED]>
> > Date: Fri, 24 Aug 2012 13:30:36
> > To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> > Reply-To: [EMAIL PROTECTED]
> > 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
Alok Kumar 2012-08-25, 12:29