[
https://issues.apache.org/jira/browse/LOG4J2-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325287#comment-16325287
]
ASF subversion and git services commented on LOG4J2-2181:
---------------------------------------------------------
Commit e46567de332419bd3612eba991f9295fcb4245bd in logging-log4j2's branch
refs/heads/master from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=e46567d ]
[LOG4J2-2181] The JDBC Appender should use keys and values from a Log4j
MapMessage. Add a new 'parameter' attribute to ColumnMapping to support
looking up a value in a MapMessage for a SQL INSERT.
> The JDBC Appender should use keys and values from a Log4j MapMessage
> --------------------------------------------------------------------
>
> Key: LOG4J2-2181
> URL: https://issues.apache.org/jira/browse/LOG4J2-2181
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Fix For: 2.10.1
>
>
> The JDBC Appender should use a keys and values for a Log4j MapMessage.
> When a {{MapMessage}} is passed to a logger API and that {{Message}} makes it
> all the way to the JDBC provider of a database {{Appender}}, then the
> resulting object sent to JDBC will have the {{MapMessage}} keys and values
> instead of the fields of the {{LogEvent}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
