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 logs a warning when one tries to override a final parameter but Hive now fails on connection startup because the client tries to set hive.aux.jars.path making beeline pretty much unusable. This only happens since https://issues.apache.org/jira/browse/HIVE-6340 was fixed as it wasn't passed on before. Is there any good reason why we can't change this behavior and instead of throwing an exception just log and ignore? I'm happy to create an issue and submit a patch just wanted to ask first if I'm missing anything. Cheers, Lars
