[ 
https://issues.apache.org/jira/browse/HIVE-11304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694329#comment-14694329
 ] 

Prasanth Jayachandran commented on HIVE-11304:
----------------------------------------------

properties file is not supported anymore. Log4j2 initialization will ignore 
properties file specified through system property log4j.configuration or the 
presence of log4j.properties in the classpath (autoloading). There is new 
system property for log4j2 for specifying the path to configuration file 
"log4j.configurationFile". If the log file is not set through this system 
property, hive's log4j configurator (LogUtils.java) will default to 
hive-log4j2.xml in classpath. If user wants to load their own configuration 
file, they should put it classpath (probably via HIVE_CONF_DIR) or use 
HIVE_OPTS to explicitly set -Dlog4j.configurationFile=<path-to-file>. The 
fallback is to use the default *log4j2.xml that is part of hive-common.jar. I 
haven't fully looked into the implication of HADOOP_USER_CLASSPATH_FIRST env 
yet (which will put the log4j2 bridge api jars first). I will confirm if that 
will have any impact on hadoop logging. [~gopalv] do you have any thoughts on 
this?

> Migrate to Log4j2 from Log4j 1.x
> --------------------------------
>
>                 Key: HIVE-11304
>                 URL: https://issues.apache.org/jira/browse/HIVE-11304
>             Project: Hive
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>         Attachments: HIVE-11304.2.patch, HIVE-11304.3.patch, 
> HIVE-11304.4.patch, HIVE-11304.5.patch, HIVE-11304.6.patch, 
> HIVE-11304.7.patch, HIVE-11304.patch
>
>
> Log4J2 has some great benefits and can benefit hive significantly. Some 
> notable features include
> 1) Performance (parametrized logging, performance when logging is disabled 
> etc.) More details can be found here 
> https://logging.apache.org/log4j/2.x/performance.html
> 2) RoutingAppender - Route logs to different log files based on MDC context 
> (useful for HS2, LLAP etc.)
> 3) Asynchronous logging
> This is an umbrella jira to track changes related to Log4j2 migration.
> Log4J1 EOL - 
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to