You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/07/06 00:25:00 UTC
[jira] [Work logged] (HIVE-26204) Unrecognized format specifier errors when running hmsbench-jar
[ https://issues.apache.org/jira/browse/HIVE-26204?focusedWorklogId=788088&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-788088 ]
ASF GitHub Bot logged work on HIVE-26204:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Jul/22 00:24
Start Date: 06/Jul/22 00:24
Worklog Time Spent: 10m
Work Description: github-actions[bot] commented on PR #3271:
URL: https://github.com/apache/hive/pull/3271#issuecomment-1175626299
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Feel free to reach out on the dev@hive.apache.org list if the patch is in need of reviews.
Issue Time Tracking
-------------------
Worklog Id: (was: 788088)
Time Spent: 20m (was: 10m)
> 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
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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.10#820010)