Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

log4j2 configuring ColumnMapping type using properties format #1405

Closed
G0-G4 opened this issue Apr 3, 2023 · 1 comment · Fixed by #1834
Closed

log4j2 configuring ColumnMapping type using properties format #1405

G0-G4 opened this issue Apr 3, 2023 · 1 comment · Fixed by #1834
Assignees
Labels
bug Incorrect, unexpected, or unintended behavior of existing code
Milestone

Comments

@G0-G4
Copy link

G0-G4 commented Apr 3, 2023

Description

It is impossible to provide ColumnMapiing type in properties format.

For example I want to write journal_id in database as an integer. I can't write something like this

appender.message_appender.columnMappings[1].type = ColumnMapping
appender.message_appender.columnMappings[1].name = journal_id
appender.message_appender.columnMappings[1].type = java.lang.Integer # can't have two type parameters

Configuration

Version: 2.11.0

Operating system: windows 10

JDK: OpenJDK 17.0.2

@ppkarwasz ppkarwasz added the bug Incorrect, unexpected, or unintended behavior of existing code label Apr 3, 2023
@ppkarwasz ppkarwasz added this to the 2.20.1 milestone Apr 3, 2023
@ppkarwasz
Copy link
Contributor

@G0-G4,

We'll try to fix the problem in the next release by adding an alternative name for the type property.

BTW: you are using a version with several security vulnerability. Upgrade to the latest one.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Incorrect, unexpected, or unintended behavior of existing code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants