kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paolo Patierno (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5481) ListOffsetResponse isn't logged in the right way with trace level enabled
Date Tue, 20 Jun 2017 12:42:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055688#comment-16055688
] 

Paolo Patierno commented on KAFKA-5481:
---------------------------------------

[~ijuma] I saw that in most cases (i.e. the related ListOffsetResponse) the toString() method
is implemented from scratch. I opened a PR in that way. Of course, having a unique way for
all the protocol messages could be better. What do you think ?

> ListOffsetResponse isn't logged in the right way with trace level enabled
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-5481
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5481
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>            Reporter: Paolo Patierno
>            Assignee: Paolo Patierno
>
> Hi,
> when trace level is enabled, the ListOffsetResponse isn't logged well but just the class
name is showed in the log  :
> {code}
> [2017-06-20 14:18:50,724] TRACE Received ListOffsetResponse org.apache.kafka.common.requests.ListOffsetResponse@7ed5ecd9
from broker new-host:9092 (id: 0 rack: null) (org.apache.kafka.clients.consumer.internals.Fetcher:674)
> {code}
> The class doesn't provide a toString() for such a thing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message