[
https://issues.apache.org/jira/browse/KAFKA-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173179#comment-17173179
]
Dongjin Lee commented on KAFKA-10329:
-------------------------------------
Hi [~rhauch],
It seems like this issue is related to [KIP-653: Upgrade log4j to
log4j2|https://cwiki.apache.org/confluence/display/KAFKA/KIP-653%3A+Upgrade+log4j+to+log4j2].
Could you have a look? In my humble opinion, it would be good to handle both
issues at once since upgrading to log4j2 inevitably introduces some backward
compatibility break.
> Enable connector context in logs by default
> -------------------------------------------
>
> Key: KAFKA-10329
> URL: https://issues.apache.org/jira/browse/KAFKA-10329
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 3.0.0
> Reporter: Randall Hauch
> Priority: Blocker
> Labels: needs-kip
> Fix For: 3.0.0
>
>
> When
> [KIP-449|https://cwiki.apache.org/confluence/display/KAFKA/KIP-449%3A+Add+connector+contexts+to+Connect+worker+logs]
> was implemented and released as part of AK 2.3, we chose to not enable these
> extra logging context information by default because it was not backward
> compatible, and anyone relying upon the `connect-log4j.properties` file
> provided by the AK distribution would after an upgrade to AK 2.3 (or later)
> see different formats for their logs, which could break any log processing
> functionality they were relying upon.
> However, we should enable this in AK 3.0, whenever that comes. Doing so will
> require a fairly minor KIP to change the `connect-log4j.properties` file
> slightly.
> Marked this as BLOCKER since it's a backward incompatible change that we
> definitely want to do in the 3.0.0 release.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
