[
https://issues.apache.org/jira/browse/KAFKA-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351622#comment-15351622
]
ASF GitHub Bot commented on KAFKA-3906:
---------------------------------------
GitHub user jcustenborder opened a pull request:
https://github.com/apache/kafka/pull/1560
KAFKA-3906 - Connect logical types do not support nulls.
Initial commit with failing unit tests for proposed functionality.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jcustenborder/kafka KAFKA-3906
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1560.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1560
----
commit 5e5d26fcb26988f1f067a91864b74f9da0851871
Author: Jeremy Custenborder <[email protected]>
Date: 2016-06-27T19:02:59Z
Modified method signatures for Date, Time, Timestamp to allow nulls. Added
tests for logical types with nulls.
----
> 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)
