[
https://issues.apache.org/jira/browse/HIVE-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Steinbach resolved HIVE-1451.
----------------------------------
Resolution: Won't Fix
Resolving this as WONTFIX for the following reasons:
# We want the Hive Metastore to be capable of handling tables stored on
different HDFS instances. Supporting this use case requires that the Metastore
store the complete address of the NN.
# HIVE-1514 added the ALTER TABLE <table> [<partition_spec>] SET LOCATION
statement which allows you to modify the storage location of a table/partition
in the metastore. This is an effective workaround for the issue described in
this ticket. Please see
https://cwiki.apache.org/Hive/languagemanual-ddl.html#LanguageManualDDL-AlterTableStorageProperties
for more information.
> Creating a table stores the full address of namenode in the metadata. This
> leads to problems when the namenode address changes.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-1451
> URL: https://issues.apache.org/jira/browse/HIVE-1451
> Project: Hive
> Issue Type: Bug
> Components: Metastore, Query Processor
> Affects Versions: 0.5.0
> Environment: Any
> Reporter: Arvind Prabhakar
>
> Here is an excerpt from table metadata for an arbitrary table {{table1}}:
> {noformat}
> hive> describe extended table1;
> OK
> ...
> Detailed Table Information ...
> location:hdfs://localhost:9000/user/arvind/hive/warehouse/table1,
> ...
> {noformat}
> As can be seen, the full address of namenode is captured in the location
> information for the table. This information is later used to run any queries
> on the table - thus making it impossible to change the namenode location once
> the table has been created. For example, for the above table, a query will
> fail if the namenode is migrated from port 9000 to 8020:
> {noformat}
> hive> select * from table1;
> OK
> Failed with exception java.io.IOException:java.net.ConnectException: Call to
> localhost/127.0.0.1:9000
> failed on connection exception: java.net.ConnectException: Connection refused
> Time taken: 10.78 seconds
> hive>
> {noformat}
> It should be possible to change the namenode location regardless of when the
> tables are created. Also, any query execution should work with the configured
> namenode at that point in time rather than requiring the configuration to be
> exactly the same at the time when the tables were created.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
