eats the purpose
of this feature and property.
Thoughts?
Mark
- Original Message -
From: "Ashutosh Chauhan"
To: dev@hive.apache.org
Cc: u...@hive.apache.org
Sent: Friday, June 1, 2012 10:24:24 AM
Subject: Re: Behavior of Hive 2837: insert into external tables should
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 n
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
(on
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 wrote:
> Hi folks,
> I have a question regarding HIVE 2837(
> https
