[ 
https://issues.apache.org/jira/browse/HIVE-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634811#comment-13634811
 ] 

Sho Shimauchi commented on HIVE-4299:
-------------------------------------

Hi [~ashutoshc],

Sorry for late.
I'm trying to write a testcase, but it's a bit hard to add a case for this 
feature.
When a table is dropped, this feature will dump a metadata in a directory which 
contains current datetime like 
/user/sho/test_table.2013-04-05-20-13-14/test_table.metadata .
I can't write IMPORT FROM query against the dynamic path.

Do you have any idea to solve this problem?

Thanks,
Sho
                
> 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

Reply via email to