[
https://issues.apache.org/jira/browse/HIVE-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702798#comment-13702798
]
Edward Capriolo commented on HIVE-4299:
---------------------------------------
[~sho.shimauchi]
You are right there is no easy way to test. Lets do this, remake your patch.
Declare a filename in either ImportSemanticAnalyzer and MetaDataExportListener
and have one reference the other, this way we do not have two strings, and we
can not have this mistake in the future.
> exported metadata by HIVE-3068 cannot be imported because of wrong file name
> ----------------------------------------------------------------------------
>
> Key: HIVE-4299
> URL: https://issues.apache.org/jira/browse/HIVE-4299
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.11.0
> Reporter: Sho Shimauchi
> Assignee: Sho Shimauchi
> Attachments: HIVE-4299.patch
>
>
> h2. Symptom
> When DROP TABLE a table, metadata of the table is generated to be able to
> import the dropped table again.
> However, the exported metadata name is '<table name>.metadata'.
> Since ImportSemanticAnalyzer allows only '_metadata' as metadata filename,
> user have to rename the metadata file to import the table.
> h2. How to reproduce
> Set the following setting to hive-site.xml:
> {code}
> <property>
> <name>hive.metastore.pre.event.listeners</name>
> <value>org.apache.hadoop.hive.ql.parse.MetaDataExportListener</value>
> </property>
> {code}
> Then run the following queries:
> {code}
> > CREATE TABLE test_table (id INT, name STRING);
> > DROP TABLE test_table;
> > IMPORT TABLE test_table_imported FROM '/path/to/metadata/file';
> FAILED: SemanticException [Error 10027]: Invalid path
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
