[ 
https://issues.apache.org/jira/browse/KAFKA-8446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Boyang Chen updated KAFKA-8446:
-------------------------------
    Description: 
To add more context here:

a NPE will be triggered in *RecordConverters#ByteBuffer.allocate(8 + 
rawValue.length)* if the raw value with record is null. A scenario you could 
reproduce is like:
 # Having a source KTable (timestampedKeyValueStore) reads in tombstone records 
where the value field is null. Note that you need to turn off stream level 
cache, otherwise the null value will not be forwarded.
 # Shutdown the application, and clear local state stores.
 # Restart the application before changelog topic starts compaction. If we are 
"lucky", the tombstone record will trigger null pointer exception during 
restoration when we try to extract raw value length.

 

> Kafka Streams restoration crashes with NPE when the record value is null
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-8446
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8446
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 2.3.0
>            Reporter: Boyang Chen
>            Assignee: Boyang Chen
>            Priority: Blocker
>
> To add more context here:
> a NPE will be triggered in *RecordConverters#ByteBuffer.allocate(8 + 
> rawValue.length)* if the raw value with record is null. A scenario you could 
> reproduce is like:
>  # Having a source KTable (timestampedKeyValueStore) reads in tombstone 
> records where the value field is null. Note that you need to turn off stream 
> level cache, otherwise the null value will not be forwarded.
>  # Shutdown the application, and clear local state stores.
>  # Restart the application before changelog topic starts compaction. If we 
> are "lucky", the tombstone record will trigger null pointer exception during 
> restoration when we try to extract raw value length.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to