[
https://issues.apache.org/jira/browse/LOG4J2-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-2181:
---------------------------------
Description:
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}}.
was:
The MongoDB 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 MongoDB provider of a NoSQL {{Appender}}, then the resulting
object sent to MongoDB will have the {{MapMessage}} keys and values instead of
the fields of the {{LogEvent}}.
> 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)
