[jira] [Created] (HIVE-7120) Beeline needs a way to work even when blacklisted properties are set

["Lars Francke (JIRA)" <ji...@apache.org>]

Lars Francke created HIVE-7120:
----------------------------------

             Summary: Beeline needs a way to work even when blacklisted properties are set
                 Key: HIVE-7120
                 URL: https://issues.apache.org/jira/browse/HIVE-7120
             Project: Hive
          Issue Type: Improvement
            Reporter: Lars Francke


Currently {{verifyAndSet}} in {{HiveConf}} throws an exception when someone tries to use a blacklisted property.

One property frequently blacklisted (by Sentry for example) is {{hive.aux.jars.path}} which is being brought into Beeline when setting an environment variable.

That means as soon as that's set (and HIVE-6340 was set) no connection can be made anymore.

My proposal would be to mimic Hadoop's behavior with {{final}} properties and instead of throwing an exception just log a warning but [~thejas] argues:

{quote}
If the verifyAndSet in HiveConf is changed to log a warning instead of
throwing an error, it would mean that any "set
<blacklisted.property>=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 would be to support ability to have a
beeline specific property, which if set does not use the common HIVE
env properties.
{quote}

Either option should be implemented I think.



--
This message was sent by Atlassian JIRA
(v6.2#6252)