[
https://issues.apache.org/jira/browse/LOG4J2-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377181#comment-16377181
]
ASF GitHub Bot commented on LOG4J2-2252:
----------------------------------------
GitHub user cakofony opened a pull request:
https://github.com/apache/logging-log4j2/pull/154
LOG4J2-2252 Reusable LogEvents should pass along the original format string
This allows custom layouts to group logged messages parameterized
values without creating new single-use messages for each event.
This slightly modifies the getFormat implementation of some
message types to avoid doing unnecessary work to load the
format string.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cakofony/logging-log4j2 LOG4J2-2252-backport
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4j2/pull/154.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 #154
----
commit ac614e85e59d9e89033eda703ec43dcd2b2b4fc7
Author: Carter Kozak <c4kofony@...>
Date: 2018-02-13T16:28:17Z
LOG4J2-2252 Reusable LogEvents should pass along the original format string
This allows custom layouts to group logged messages parameterized
values without creating new single-use messages for each event.
This slightly modifies the getFormat implementation of some
message types to avoid doing unnecessary work to load the
format string.
----
> Reusable events drop the original format string
> -----------------------------------------------
>
> Key: LOG4J2-2252
> URL: https://issues.apache.org/jira/browse/LOG4J2-2252
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Carter Douglas Kozak
> Assignee: Remko Popma
> Priority: Major
>
> MutableLogEvent and RingBufferLogEvent hold references to state from original
> messages, but they currently exclude the value of Message.getFormat().
> I would like to write a custom Layout implementation which is aware of the
> format string and parameters, which doesn't necessarily use the formatted
> message value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
