title: After log4j changes Hive -e returns additional warning which has impact on the scripts - WARN JNDI lookup class is not available because this JRE
body: <p>In project we use some technical scripts in python with usage of Subprocess to extract some data from hive, run msck repair table etc ( I know we should switch to beeline :p) unfortunately after the issue with log4j in every output we started to get something like this:</p>
  <p>WARN JNDI lookup class is not available because this JRE does not support JNDI. JNDI string lookups will not be available, continuing configuration. Ignoring java.lang.ClassNotFoundException: org.apache.logging.log4j.core.lookup.JndiLookup</p>
  <p>Our Infra team is not allowing us so far to introduce any changes in the log4j properties.</p>
  <p>As we have multiple technical scripts in many places we would like to find simple solution for time being (till we can fix it on infra level).</p>
  <p>Tried:
  usage hive -s
  settings hive.root.looger to console (I think somehow log4j does not understand this is warning)</p>
  <p>Guys does anyone know how we can fix it (preferably during runtime)</p>
  <p>Thanks!</p>