I am a bit confused by this feature too especialyl since hive now has
a lock table function. Changing existing semantics would be bad.
Different storage handlers actually treat external differently as
well.
On 6/1/12, Mark Grover grover.markgro...@gmail.com wrote:
Hi folks,
I have a question
Well now hive has a property
hive.insert.into.external.tables which is true by default.
So the default behaviour/semantics is unchange unless the switch is
thrown. That is a fair compromise all be it semi confusing when there
is already two other ways to prevent someone from editing the table
Hi Mark,
I understand your concern w.r.t backward compatibility. But as Ed pointed
out there is a config variable and by default semantic is unchanged so you
can continue to insert into your external table.
I have a question though. Why are you creating all your tables as
external tables ? Why
Thanks, Ashutosh and Ed.
Historically, I didn't have much reason choose managed over external tables or
vice-versa since the semantics were very similar. I chose external because it
allowed me a better handle on the table metadata. For example, if a new column
got added to the file, I could
Hi folks,
I have a question regarding HIVE 2837(
https://issues.apache.org/jira/browse/HIVE-2837) that deals with
disallowing external table from using insert into queries.
From looking at the JIRA, it seems like it applies to external tables on
HDFS as well. Technically, insert into should be ok
