[
https://issues.apache.org/jira/browse/HIVE-11304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005687#comment-15005687
]
Xuefu Zhang commented on HIVE-11304:
------------------------------------
[~prasanth_j], it looks like that this has broken Spark test in such a way that
no hive.log is generated. To reproduce, run the following in itests/:
{code}
mvn test -Dtest=TestSparkCliDriver -Dqfile=orc_merge1.q -Phadoop-2
{code}
Reverting the patch here fixes the problem. The following is the location of
the expected hive.log:
{code}
./itests/qtest-spark/target/tmp/log/hive.log
{code}
Please take a look.
> Migrate to Log4j2 from Log4j 1.x
> --------------------------------
>
> Key: HIVE-11304
> URL: https://issues.apache.org/jira/browse/HIVE-11304
> Project: Hive
> Issue Type: Improvement
> Components: Logging
> Affects Versions: 2.0.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Labels: TODOC2.0, incompatibleChange
> Fix For: 2.0.0
>
> Attachments: HIVE-11304.10.patch, HIVE-11304.11.patch,
> 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.8.patch, HIVE-11304.9.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)
