Yes, I changed ports after creating certain tables (started using
Derby). New tables created do not have this issue. I will simply drop
and recreate the tables since I have that option in this case.
Thanks for the comments!
-M@
On Tue, Sep 28, 2010 at 8:54 PM, Adarsh Sharma
That sounded easier than said. The same problem that won't allow me to
select from the tables, won't allow me to drop them. How can I just
refresh the metadata?
On Wed, Sep 29, 2010 at 8:00 AM, Matt Tanquary matt.tanqu...@gmail.com wrote:
Yes, I changed ports after creating certain tables
Since I'm using derby, I went to $DERBY_HOME/data and moved
metastore_db to metastore_db_save and restarted derby. The next time I
started Hive, the metastore_db was recreated.
On Wed, Sep 29, 2010 at 8:21 AM, Matt Tanquary matt.tanqu...@gmail.com wrote:
That sounded easier than said. The same
Here is what might be happening:
1 You were running namenode on port 8020
2 Your hive meta data was set based on that. (Table location on hdfs)
3 You changed the namenode port (but hive meta data doesnt know about it)
4 'show tables' is still trying to find tables in
hdfs:host:8020/table_path
I
Hi, what we did what Shrijeet said, we changed our hdfs port to 8020 because
we didn't know where to change it.
It is a filthy workaround but as we are still testing Hive, we just let that
one pass.
Maybe someone knows a dirty way to change Hive's port, I would also be
happy to try it.
And
Renato,
I did not change it personally , ever. My observation comes from the fact
that hive meta data stores location of a table (an hdfs path). I am using
mysql to store meta data. In my case, the mysql table 'SDS' has location
information, for example the table named medex has location set in
May these few things solve the error :-
1. Check through web interface wheteher the namenode, jobtracker,
tasktracker are running or not.
2. Resolve IP-host name binding to edit /etc/hosts file of all nodes.
Insert these lines
IP-addresss hostname
e. g 192.122.0.111 node1
Thanks
Matt
