[LOG4J2-2181] The JDBC Appender should use keys and values from a Log4j MapMessage

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.11.0
• Component/s: Appenders
• Assignee: Gary D. Gregory
• Reporter: Gary D. Gregory
• Created: 11/Jan/18 04:12
• Updated: 13/Jan/18 21:59
• Resolved: 12/Jan/18 01:18

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.

Issue Links

• is a clone of: LOG4J2-2179 The MongoDB Appender should use keys and values from a Log4j MapMessage
• is blocked by: LOG4J2-2180 Add a MongoDbProvider builder for and deprecate org.apache.logging.log4j.mongodb.MongoDbProvider.createNoSqlProvider()