Matt – changing the DNS resolved the Hive errors, but led to other issues
which I'm afraid I can't remember right now. I just remember the change
broke something else, so the best course seemed to be to fix the metadata.
This of course doesn't mean you'll hit the same issue, but on the other
hand i
Hi Jon,
I've just encountered the same issue.
I was wondering if you would be so kind as to elaborate, on why you'd be
best off manipulating the metadata as opposed to trying to manipulate the
DNS?
I had a go at having the Namenode use a dns alias Namenode, then the hive
metadata did indeed conta
Varun – So yes, Hive stores the full URI to the NameNode in the metadata
for every table and partition. From my experience you're best off modifying
the metadata to point to the new NN, as opposed to trying to manipulate
DNS. Fortunately, this is fairly straightforward since there's mainly one
colu
A hive table stores the full HDFS URI to the table such as
hdfs://hostname:9120/user/hive/warehouse
You likely have restored you name node to a different hostname and now
hive is not able to locate it.
You might be able to create a DNS cname to resolve this.
Hind sight, is 20/20 but I would hav
Hi All,
I have changed the namenode from one server to another when there was a
crash of hardware.
After configuring the Namenode.
When i am executing hive query below error is shown..
bin/hive -e “insert overwrite table pokes select a.* from invites a where
a.ds=’2008-08-15′;”
Hive history
fil
