[ https://issues.apache.org/jira/browse/KAFKA-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shikhar Bhushan resolved KAFKA-3906. ------------------------------------ Resolution: Fixed I think we should handle null values at the converter layer to avoid duplication in logical type impls, as [~ewencp] suggested in the PR. KAFKA-4183 fixes the null handling for logical types in {{JsonConverter}}. > Connect logical types do not support nulls. > ------------------------------------------- > > Key: KAFKA-3906 > URL: https://issues.apache.org/jira/browse/KAFKA-3906 > Project: Kafka > Issue Type: Bug > Components: KafkaConnect > Affects Versions: 0.10.0.0 > Reporter: Jeremy Custenborder > Assignee: Ewen Cheslack-Postava > > The logical types for Kafka Connect do not support null data values. Date, > Decimal, Time, and Timestamp all will throw null reference exceptions if a > null is passed in to their fromLogical and toLogical methods. Date, Time, and > Timestamp require signature changes for these methods to support nullable > types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)