[
https://issues.apache.org/jira/browse/HIVE-11304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694335#comment-14694335
]
Prasanth Jayachandran commented on HIVE-11304:
----------------------------------------------
[~sershe] Yes. The xml files are functionally equivalent to that of old
properties files. Only one difference though, some old properties flag had
wrong spelling for log4j.threshold (it had "threshhold") which will use the
default threshold of DEBUG in log4j1.x. Even though the config meant to set ALL
threshold because of the wrong spelling it defaulted to DEBUG. Thats fixed in
new configs.
> 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)
