[KAFKA-16795] Fix broken compatibility in kafka.tools.NoOpMessageFormatter, kafka.tools.DefaultMessageFormatter, and kafka.tools.LoggingMessageFormatter

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.8.0
• Assignee: Kuan Po Tseng
• Reporter: Kuan Po Tseng
• Created: 19/May/24 08:46
• Updated: 23/May/24 18:54
• Resolved: 23/May/24 18:52

Description

0bf830f moved NoOpMessageFormatter, DefaultMessageFormatter and LoggingMessageFormatter package from kafka.tools to org.apache.kafka.tools.consumer{}

These classes could be used via cmd kafka-console-consumer.sh. We should have a dependency cycle before 3.8.0 comes out.

 

bin/kafka-console-consumer.sh --bootstrap-server localhost:9092 \
    --topic streams-wordcount-output \
    --from-beginning \
    --formatter kafka.tools.DefaultMessageFormatter \
    --property print.key=true \
    --property print.value=true \
    --property key.deserializer=org.apache.kafka.common.serialization.StringDeserializer \
    --property value.deserializer=org.apache.kafka.common.serialization.LongDeserializer

The goal in this Jira is to allow user to keep using kafka.tools.NoOpMessageFormatter, kafka.tools.DefaultMessageFormatter, and kafka.tools.LoggingMessageFormatter, but we also display warning messages to say those "strings" will be removed in 4.0.

 

Issue Links

• links to: GitHub Pull Request #16020