[
https://issues.apache.org/jira/browse/HIVE-26204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu-Wen Lai updated HIVE-26204:
------------------------------
Summary: Unrecognized format specifier errors when running hmsbench-jar
(was: Unrecognized format specifier error when running hmsbench-jar)
> Unrecognized format specifier errors when running hmsbench-jar
> --------------------------------------------------------------
>
> Key: HIVE-26204
> URL: https://issues.apache.org/jira/browse/HIVE-26204
> Project: Hive
> Issue Type: Improvement
> Components: Standalone Metastore
> Reporter: Yu-Wen Lai
> Assignee: Yu-Wen Lai
> Priority: Major
>
> Here is the logging error.
> {code:java}
> ERROR StatusLogger Unrecognized format specifier [d]
> ERROR StatusLogger Unrecognized conversion specifier [d] starting at position
> 16 in conversion pattern.
> ERROR StatusLogger Unrecognized format specifier [thread]
> ERROR StatusLogger Unrecognized conversion specifier [thread] starting at
> position 25 in conversion pattern.
> ERROR StatusLogger Unrecognized format specifier [level]
> ERROR StatusLogger Unrecognized conversion specifier [level] starting at
> position 35 in conversion pattern.
> ERROR StatusLogger Unrecognized format specifier [logger]
> ERROR StatusLogger Unrecognized conversion specifier [logger] starting at
> position 47 in conversion pattern.
> ERROR StatusLogger Unrecognized format specifier [msg]
> ERROR StatusLogger Unrecognized conversion specifier [msg] starting at
> position 54 in conversion pattern.
> ERROR StatusLogger Unrecognized format specifier [n]
> ERROR StatusLogger Unrecognized conversion specifier [n] starting at position
> 56 in conversion pattern.{code}
> The issue is because only one Log4j2Plugins.dat is survived when the jar file
> is assembled. One way to avoid this issue is that we exclude this file and
> let log4j to load plugins on the fly.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
