[jira] [Comment Edited] (KAFKA-6685) Connect deserialization log message should distinguish key from value
[ https://issues.apache.org/jira/browse/KAFKA-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406081#comment-16406081 ] Jagadesh Adireddi edited comment on KAFKA-6685 at 3/22/18 12:28 PM: Hi [~rhauch], I would like to pick this Jira up. Wanted some advice on the error message .I am thinking , if the exception occurred during: a) keyAndSchema conversion, then error msg logged as : Failed to convert Record Key to Kafka Connect format. b) valueAndSchema conversion, then error msg logged as : Failed to convert Record Value to Kafka Connect format. And Main ConnectException thrown as : Exiting WorkerSinkTask due to unconvertedmessage exception. Any help on the hint message to fix the issue would be great? was (Author: adireddijagad...@gmail.com): Hi [~rhauch], I would like to pick this Jira up. Wanted some advice on the error message .I am thinking , if the exception occurred during: a) keyAndSchema conversion, then error msg logged as : Failed to convert message Key And Schema to Kafka Connect format. b) valueAndSchema conversion, then error msg logged as : Failed to convert message Value And Schema to Kafka Connect format. And Main ConnectException thrown as : Exiting WorkerSinkTask due to unconvertedmessage exception. Any help on the hint message to fix the issue would be great? > Connect deserialization log message should distinguish key from value > - > > Key: KAFKA-6685 > URL: https://issues.apache.org/jira/browse/KAFKA-6685 > Project: Kafka > Issue Type: Improvement > Components: KafkaConnect >Reporter: Yeva Byzek >Priority: Minor > Labels: newbie > > Connect was configured for Avro key and value but data had String key and > Avro value. The resulting error message was misleading because it didn't > distinguish key from value, and so I was chasing problems with the value > instead of the key. > tl;dr Connect should at least tell you whether the problem is with > deserializing the key or value of a record > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KAFKA-6685) Connect deserialization log message should distinguish key from value
[ https://issues.apache.org/jira/browse/KAFKA-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406081#comment-16406081 ] Jagadesh Adireddi edited comment on KAFKA-6685 at 3/20/18 10:25 AM: Hi [~rhauch], I would like to pick this Jira up. Wanted some advice on the error message .I am thinking , if the exception occurred during: a) keyAndSchema conversion, then error msg logged as : Failed to convert message Key And Schema to Kafka Connect format. b) valueAndSchema conversion, then error msg logged as : Failed to convert message Value And Schema to Kafka Connect format. And Main ConnectException thrown as : Exiting WorkerSinkTask due to unconvertedmessage exception. Any help on the hint message to fix the issue would be great? was (Author: adireddijagad...@gmail.com): Hi [~rhauch], I would like to pick this Jira up. Wanted some advice on the error message . I am thinking , if the exception occurred during: a) keyAndSchema conversion, then error msg logged as : Failed to convert message Key And Schema to Kafka Connect format. b) valueAndSchema conversion, then error msg logged as : Failed to convert message Value And Schema to Kafka Connect format. And Main ConnectException thrown as : Exiting WorkerSinkTask due to unconvertedmessage exception. Any help on the hint message to fix the issue would be great? > Connect deserialization log message should distinguish key from value > - > > Key: KAFKA-6685 > URL: https://issues.apache.org/jira/browse/KAFKA-6685 > Project: Kafka > Issue Type: Improvement > Components: KafkaConnect >Reporter: Yeva Byzek >Priority: Minor > Labels: newbie > > Connect was configured for Avro key and value but data had String key and > Avro value. The resulting error message was misleading because it didn't > distinguish key from value, and so I was chasing problems with the value > instead of the key. > tl;dr Connect should at least tell you whether the problem is with > deserializing the key or value of a record > -- This message was sent by Atlassian JIRA (v7.6.3#76005)