[
https://issues.apache.org/jira/browse/KAFKA-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098604#comment-15098604
]
Jason Gustafson commented on KAFKA-2695:
----------------------------------------
[~junrao] That actually works currently because records are not parsed using
o.a.k.common.protocol.types.Type. But most other cases will fail because the
parsing code looks like this:
{code}
int length = buffer.getShort();
byte[] bytes = new byte[length];
{code}
It's not difficult to fix, but we'll probably need to make sure that current
usage can handle null values without breaking in other ways.
> Handle null string/bytes protocol primitives
> --------------------------------------------
>
> Key: KAFKA-2695
> URL: https://issues.apache.org/jira/browse/KAFKA-2695
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
>
> The kafka protocol supports null bytes and string primitives by passing -1 as
> the size, but the current deserializers implemented in
> o.a.k.common.protocol.types.Type do not handle them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
