Kuan Po Tseng created KAFKA-16795:
-------------------------------------
Summary: Fix broken compatibility in
kafka.tools.NoOpMessageFormatter, kafka.tools.DefaultMessageFormatter, and
kafka.tools.LoggingMessageFormatter
Key: KAFKA-16795
URL: https://issues.apache.org/jira/browse/KAFKA-16795
Project: Kafka
Issue Type: Bug
Reporter: Kuan Po Tseng
Assignee: Kuan Po Tseng
Fix For: 3.8.0
[{{0bf830f}}|https://github.com/apache/kafka/commit/0bf830fc9c3915bc99b6e487e6083dabd593c5d3]
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.
{code:java}
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{code}
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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
