[
https://issues.apache.org/jira/browse/LOG4J2-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244789#comment-16244789
]
ASF GitHub Bot commented on LOG4J2-2107:
----------------------------------------
GitHub user cakofony opened a pull request:
https://github.com/apache/logging-log4j2/pull/126
LOG4J2-2107: MapMessage allocation-free pattern conversion
Fixes an issue causing MessagePatternConverter to greedily format
MapMessage instances as StringBuilderFormattable ignoring format.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cakofony/logging-log4j2 LOG4J2-2107
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4j2/pull/126.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #126
----
commit 5042cf07077ebf16acd018cee33d5f5867711d38
Author: Carter Kozak <[email protected]>
Date: 2017-11-08T21:53:31Z
LOG4J2-2107: MapMessage allocation-free pattern conversion
Fixes an issue causing MessagePatternConverter to greedily format
MapMessage instances as StringBuilderFormattable ignoring format.
----
> MapMessage should support both StringBuilderFormattable and MultiformatMessage
> ------------------------------------------------------------------------------
>
> Key: LOG4J2-2107
> URL: https://issues.apache.org/jira/browse/LOG4J2-2107
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts
> Affects Versions: 2.9.1
> Reporter: Carter Douglas Kozak
>
> Currently MessagePatternConverter will not respect the format, writing the
> MapMessage directly to a shared StringBuilder using the default encoding.
> We need to implement a "MultiFormatStringBuilderFormattable" type with "void
> formatTo(String[] formats, StringBuilder buffer);"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
