You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Craig Swift (Created) (JIRA)" <ji...@apache.org> on 2012/03/21 17:43:51 UTC
[jira] [Created] (HIVE-2888) Creating an external table using the
'LIKE' clause actually creates a managed table.
Creating an external table using the 'LIKE' clause actually creates a managed table.
------------------------------------------------------------------------------------
Key: HIVE-2888
URL: https://issues.apache.org/jira/browse/HIVE-2888
Project: Hive
Issue Type: Bug
Components: Metastore
Affects Versions: 0.7.1
Reporter: Craig Swift
When creating a new table with both the EXTERNAL and LIKE clauses, the new table does not behave as an EXTERNAL table thus resulting in potential data loss.
Example:
create external table test1 (VAL string) location '/user/craig/test1';
create external table test2 like test1 location '/user/craig/test2';
drop table test1;
/user/craig/test1 - still exists
drop table test2;
/user/craig/test2 - is deleted (bad)
If I do an extended describe on both tables, test1 shows up as being external while test2 is a managed table.
--
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
[jira] [Resolved] (HIVE-2888) Creating an external table using the
'LIKE' clause actually creates a managed table.
Posted by "Ashutosh Chauhan (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashutosh Chauhan resolved HIVE-2888.
------------------------------------
Resolution: Fixed
Fix Version/s: 0.8.0
Fixed in HIVE-2086.
> Creating an external table using the 'LIKE' clause actually creates a managed table.
> ------------------------------------------------------------------------------------
>
> Key: HIVE-2888
> URL: https://issues.apache.org/jira/browse/HIVE-2888
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.7.1
> Reporter: Craig Swift
> Fix For: 0.8.0
>
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> When creating a new table with both the EXTERNAL and LIKE clauses, the new table does not behave as an EXTERNAL table thus resulting in potential data loss.
> Example:
> create external table test1 (VAL string) location '/user/craig/test1';
> create external table test2 like test1 location '/user/craig/test2';
> drop table test1;
> /user/craig/test1 - still exists
> drop table test2;
> /user/craig/test2 - is deleted (bad)
> If I do an extended describe on both tables, test1 shows up as being external while test2 is a managed table.
--
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
[jira] [Commented] (HIVE-2888) Creating an external table using the
'LIKE' clause actually creates a managed table.
Posted by "Kai Zhang (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252183#comment-13252183 ]
Kai Zhang commented on HIVE-2888:
---------------------------------
This has been fixed in HIVE-2086.
> Creating an external table using the 'LIKE' clause actually creates a managed table.
> ------------------------------------------------------------------------------------
>
> Key: HIVE-2888
> URL: https://issues.apache.org/jira/browse/HIVE-2888
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.7.1
> Reporter: Craig Swift
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> When creating a new table with both the EXTERNAL and LIKE clauses, the new table does not behave as an EXTERNAL table thus resulting in potential data loss.
> Example:
> create external table test1 (VAL string) location '/user/craig/test1';
> create external table test2 like test1 location '/user/craig/test2';
> drop table test1;
> /user/craig/test1 - still exists
> drop table test2;
> /user/craig/test2 - is deleted (bad)
> If I do an extended describe on both tables, test1 shows up as being external while test2 is a managed table.
--
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