That's RocksDB .. I'm using in-memory stores ... here: https://github.com/apache/kafka/blob/0.11.0/streams/src/main/java/org/apache/kafka/streams/state/internals/ChangeLoggingKeyValueBytesStore.java#L56 the 'null' is not checked ...
On Tue, Aug 8, 2017 at 12:52 PM, Damian Guy <damian....@gmail.com> wrote: > Hi, > The null values are treated as deletes when they are written to the store. > You can see here: > https://github.com/apache/kafka/blob/0.11.0/streams/src/ > main/java/org/apache/kafka/streams/state/internals/RocksDBStore.java#L261 > > On Tue, 8 Aug 2017 at 11:22 Bart Vercammen <b...@cloutrix.com> wrote: > > > Hi, > > > > I noticed the following: > > When a kafka streams application starts, it will restore its state in its > > state-stores (from the log-compacted kafka topic). All good so far, but > I > > noticed that the 'deleted' entries are actually read in into the store as > > 'key' with value:`null` > > > > Is this expected behaviour? I would assume that 'null' values are > ignored > > when restoring the state as this is exactly how the entries are deleted > on > > the log-compacted kafka-topic. > > > > When the compaction has run on the kafka topic, all is fine, but when the > > segment is not compacted yet, these null values are read in. > > > > Greets, > > Bart > > > -- Mvg, Bart Vercammen clouTrix BVBA +32 486 69 17 68 i...@cloutrix.com
