I see what you mean. I'm not sure I fully agree but that sounds like
what we do agree on is that something should be changed. I'll open an
issue.
Thanks for your input.
On Thu, May 22, 2014 at 10:17 PM, Thejas Nair wrote:
> If the verifyAndSet in HiveConf is changed to log a warning instead of
>
If the verifyAndSet in HiveConf is changed to log a warning instead of
throwing an error, it would mean that any "set
=abc;" would result in a warning instead of an
error.
This would not be the right behavior IMO, a command that did not
succeed should throw an error.
I think a better approach woul
Hi,
I've just run into a problem with verifyAndSet in HiveConf. It throws
an exception when someone tries to use a blacklisted property. We've
blacklisted hive.aux.jars.path amongst others.
But we're using the same environment variables for client and server.
With Hadoop this is no problem, it lo
