[
https://issues.apache.org/jira/browse/AVRO-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955194#comment-17955194
]
Oscar Westra van Holthe - Kind commented on AVRO-3791:
------------------------------------------------------
The (merged) PR implements the errors for the classic reader, but does not
implement the error messages for the new fastreader, which is going to become
the default.
> [Java] "Found null, expecting <Type>" error should specify field to user
> ------------------------------------------------------------------------
>
> Key: AVRO-3791
> URL: https://issues.apache.org/jira/browse/AVRO-3791
> Project: Apache Avro
> Issue Type: Improvement
> Components: java
> Reporter: Logan Donoughe
> Priority: Trivial
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> When working with Avro and Flink, I've run into errors like this fairly
> often:
> {code:java}
> java.io.IOException: Failed to deserialize consumer record due to
> ...
> Caused by: org.apache.avro.AvroTypeException: Found null, expecting string
> at
> org.apache.avro.io.ResolvingDecoder.doAction(ResolvingDecoder.java:308) {code}
> At a glance, this is not particularly useful. I know that some field is
> getting a null where there is a non-nullable string but in order to find out
> which one it is I either have to check all possible non-null string fields
> for null values, look at which columns are changed recently and guess and
> check, or throw a debugger in and dive down the stack. So far, the last has
> been the fastest for me.
> Ideally, I would like the error message to tell me which field has the null
> value so I can fix the problem with high confidence and without the use of a
> debugger.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
