[jira] [Updated] (KAFKA-9018) Kafka Connect - throw clearer exceptions on serialisation errors
[
https://issues.apache.org/jira/browse/KAFKA-9018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Hauch updated KAFKA-9018:
-
Fix Version/s: (was: 2.6.0)
2.7.0
Since this is not a blocker issue, as part of the 2.6.0 release process I'm
changing the fix version to `2.7.0`. If this is incorrect, please respond and
discuss on the "[DISCUSS] Apache Kafka 2.6.0 release" discussion mailing list
thread.
> Kafka Connect - throw clearer exceptions on serialisation errors
>
>
> Key: KAFKA-9018
> URL: https://issues.apache.org/jira/browse/KAFKA-9018
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
>Affects Versions: 2.5.0, 2.4.1
>Reporter: Robin Moffatt
>Assignee: Mario Molina
>Priority: Minor
> Fix For: 2.7.0
>
>
> When Connect fails on a deserialisation error, it doesn't show if that's the
> *key or value* that's thrown the error, nor does it give the user any
> indication of the *topic/partition/offset* of the message. Kafka Connect
> should be improved to return this information.
> Example message that user will get (in this case caused by reading non-Avro
> data with the Avro converter)
> {code:java}
> Caused by: org.apache.kafka.connect.errors.DataException: Failed to
> deserialize data for topic sample_topic to Avro:
> at
> io.confluent.connect.avro.AvroConverter.toConnectData(AvroConverter.java:110)
> at
> org.apache.kafka.connect.runtime.WorkerSinkTask.lambda$convertAndTransformRecord$1(WorkerSinkTask.java:487)
> at
> org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndRetry(RetryWithToleranceOperator.java:128)
> at
> org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndHandleError(RetryWithToleranceOperator.java:162)
> ... 13 more
> Caused by: org.apache.kafka.common.errors.SerializationException: Error
> deserializing Avro message for id -1
> Caused by: org.apache.kafka.common.errors.SerializationException: Unknown
> magic byte!{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KAFKA-9018) Kafka Connect - throw clearer exceptions on serialisation errors
[
https://issues.apache.org/jira/browse/KAFKA-9018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Molina updated KAFKA-9018:
Fix Version/s: 2.6.0
> Kafka Connect - throw clearer exceptions on serialisation errors
>
>
> Key: KAFKA-9018
> URL: https://issues.apache.org/jira/browse/KAFKA-9018
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
>Affects Versions: 2.5.0, 2.4.1
>Reporter: Robin Moffatt
>Assignee: Mario Molina
>Priority: Minor
> Fix For: 2.6.0
>
>
> When Connect fails on a deserialisation error, it doesn't show if that's the
> *key or value* that's thrown the error, nor does it give the user any
> indication of the *topic/partition/offset* of the message. Kafka Connect
> should be improved to return this information.
> Example message that user will get (in this case caused by reading non-Avro
> data with the Avro converter)
> {code:java}
> Caused by: org.apache.kafka.connect.errors.DataException: Failed to
> deserialize data for topic sample_topic to Avro:
> at
> io.confluent.connect.avro.AvroConverter.toConnectData(AvroConverter.java:110)
> at
> org.apache.kafka.connect.runtime.WorkerSinkTask.lambda$convertAndTransformRecord$1(WorkerSinkTask.java:487)
> at
> org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndRetry(RetryWithToleranceOperator.java:128)
> at
> org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndHandleError(RetryWithToleranceOperator.java:162)
> ... 13 more
> Caused by: org.apache.kafka.common.errors.SerializationException: Error
> deserializing Avro message for id -1
> Caused by: org.apache.kafka.common.errors.SerializationException: Unknown
> magic byte!{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KAFKA-9018) Kafka Connect - throw clearer exceptions on serialisation errors
[
https://issues.apache.org/jira/browse/KAFKA-9018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Molina updated KAFKA-9018:
Affects Version/s: 2.5.0
2.4.1
> Kafka Connect - throw clearer exceptions on serialisation errors
>
>
> Key: KAFKA-9018
> URL: https://issues.apache.org/jira/browse/KAFKA-9018
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
>Affects Versions: 2.5.0, 2.4.1
>Reporter: Robin Moffatt
>Assignee: Mario Molina
>Priority: Minor
>
> When Connect fails on a deserialisation error, it doesn't show if that's the
> *key or value* that's thrown the error, nor does it give the user any
> indication of the *topic/partition/offset* of the message. Kafka Connect
> should be improved to return this information.
> Example message that user will get (in this case caused by reading non-Avro
> data with the Avro converter)
> {code:java}
> Caused by: org.apache.kafka.connect.errors.DataException: Failed to
> deserialize data for topic sample_topic to Avro:
> at
> io.confluent.connect.avro.AvroConverter.toConnectData(AvroConverter.java:110)
> at
> org.apache.kafka.connect.runtime.WorkerSinkTask.lambda$convertAndTransformRecord$1(WorkerSinkTask.java:487)
> at
> org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndRetry(RetryWithToleranceOperator.java:128)
> at
> org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndHandleError(RetryWithToleranceOperator.java:162)
> ... 13 more
> Caused by: org.apache.kafka.common.errors.SerializationException: Error
> deserializing Avro message for id -1
> Caused by: org.apache.kafka.common.errors.SerializationException: Unknown
> magic byte!{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KAFKA-9018) Kafka Connect - throw clearer exceptions on serialisation errors
[
https://issues.apache.org/jira/browse/KAFKA-9018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Moffatt updated KAFKA-9018:
-
Description:
When Connect fails on a deserialisation error, it doesn't show if that's the
*key or value* that's thrown the error, nor does it give the user any
indication of the *topic/partition/offset* of the message. Kafka Connect should
be improved to return this information.
Example message that user will get (in this case caused by reading non-Avro
data with the Avro converter)
{code:java}
Caused by: org.apache.kafka.connect.errors.DataException: Failed to deserialize
data for topic sample_topic to Avro:
at
io.confluent.connect.avro.AvroConverter.toConnectData(AvroConverter.java:110)
at
org.apache.kafka.connect.runtime.WorkerSinkTask.lambda$convertAndTransformRecord$1(WorkerSinkTask.java:487)
at
org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndRetry(RetryWithToleranceOperator.java:128)
at
org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndHandleError(RetryWithToleranceOperator.java:162)
... 13 more
Caused by: org.apache.kafka.common.errors.SerializationException: Error
deserializing Avro message for id -1
Caused by: org.apache.kafka.common.errors.SerializationException: Unknown
magic byte!{code}
was:
When Connect fails on a deserialisation error, it doesn't show if that's the
*key or value* that's thrown the error, nor does it give the user any
indication of the *topic/partition/offset* of the message. Kafka Connect should
be improved to return this information.
Caused by: org.apache.kafka.connect.errors.DataException: Failed to deserialize
data for topic sample_topic to Avro:
at
io.confluent.connect.avro.AvroConverter.toConnectData(AvroConverter.java:110)
at
org.apache.kafka.connect.runtime.WorkerSinkTask.lambda$convertAndTransformRecord$1(WorkerSinkTask.java:487)
at
org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndRetry(RetryWithToleranceOperator.java:128)
at
org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndHandleError(RetryWithToleranceOperator.java:162)
... 13 more
Caused by: org.apache.kafka.common.errors.SerializationException: Error
deserializing Avro message for id -1
Caused by: org.apache.kafka.common.errors.SerializationException: Unknown magic
byte!
> Kafka Connect - throw clearer exceptions on serialisation errors
>
>
> Key: KAFKA-9018
> URL: https://issues.apache.org/jira/browse/KAFKA-9018
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
>Reporter: Robin Moffatt
>Priority: Minor
>
> When Connect fails on a deserialisation error, it doesn't show if that's the
> *key or value* that's thrown the error, nor does it give the user any
> indication of the *topic/partition/offset* of the message. Kafka Connect
> should be improved to return this information.
> Example message that user will get (in this case caused by reading non-Avro
> data with the Avro converter)
> {code:java}
> Caused by: org.apache.kafka.connect.errors.DataException: Failed to
> deserialize data for topic sample_topic to Avro:
> at
> io.confluent.connect.avro.AvroConverter.toConnectData(AvroConverter.java:110)
> at
> org.apache.kafka.connect.runtime.WorkerSinkTask.lambda$convertAndTransformRecord$1(WorkerSinkTask.java:487)
> at
> org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndRetry(RetryWithToleranceOperator.java:128)
> at
> org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndHandleError(RetryWithToleranceOperator.java:162)
> ... 13 more
> Caused by: org.apache.kafka.common.errors.SerializationException: Error
> deserializing Avro message for id -1
> Caused by: org.apache.kafka.common.errors.SerializationException: Unknown
> magic byte!{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
