[ 
https://issues.apache.org/jira/browse/CAMEL-17509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Otavio Rodolfo Piske updated CAMEL-17509:
-----------------------------------------
    Description: 
There are several circumstances in the consumer when we refer to the topic name 
in log messages (for example [1]). However, the code may not necessarily need 
to be connected to a single topic as we support topic patterns.

Our log messages should be clearer about this.

 

1. 
[https://github.com/apache/camel/blob/camel-3.14.0/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaFetchRecords.java#L247-L260]

  was:
There are several circumstances in the consumer when we refer to the topic name 
in log messages (for example [1]). However, the code may not necessarily is 
connect to a single topic as we support topic patterns.

Our log messages should be clearer about this.

 

1. 
https://github.com/apache/camel/blob/camel-3.14.0/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaFetchRecords.java#L247-L260


> camel-kafka: invalid topic info displayed when using topic patterns
> -------------------------------------------------------------------
>
>                 Key: CAMEL-17509
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17509
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-kafka
>            Reporter: Otavio Rodolfo Piske
>            Assignee: Otavio Rodolfo Piske
>            Priority: Major
>
> There are several circumstances in the consumer when we refer to the topic 
> name in log messages (for example [1]). However, the code may not necessarily 
> need to be connected to a single topic as we support topic patterns.
> Our log messages should be clearer about this.
>  
> 1. 
> [https://github.com/apache/camel/blob/camel-3.14.0/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaFetchRecords.java#L247-L260]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to