[
https://issues.apache.org/jira/browse/HIVE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286907#comment-13286907
]
Mark Grover commented on HIVE-2837:
-----------------------------------
>From looking at this, it seems like it applies to external tables on HDFS as
>well. Can you please confirm this is correct?
Technically, insert into should be ok for external tables on HDFS (and S3) as
well. Seems like a storage file system level thing to specify whether insert
into is applied and implement it.
Some context for you:
Historically, there hasn't been any real difference between creating an
external table on HDFS vs creating a managed one. However, if we disallow
insert into on external tables, that would mean that folks with external tables
on HDFS wouldn't be able to make use of insert into functionality even though
they should be able to. This would make new tables to be biased towards managed
tables but what about the people who already have their entire Hive warehouses
based on external tables?
> insert into external tables should not be allowed
> -------------------------------------------------
>
> Key: HIVE-2837
> URL: https://issues.apache.org/jira/browse/HIVE-2837
> Project: Hive
> Issue Type: Bug
> Reporter: Namit Jain
> Assignee: Namit Jain
> Fix For: 0.9.0
>
> Attachments: HIVE-2837.D2211.1.patch, HIVE-2837.D2211.2.patch
>
>
> This is a very risky thing to allow.
> Since, the external tables can point to any user location, which can
> potentially corrupt some other tables.
--
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
