Our use case for kafka-streams only needs to use the in memory state store but 
the current code on trunk still requires a valid ’state.dir’ that the client 
can write too.  A lock file per partition and an offset file is created but the 
offset file always contains zero values for offsets since all the state is 
described by the state topic.  I have a patch that removes this dependency but 
was wondering whether there might be a reason to keep the ability to write out 
the offset in some future improvement to the in memory state store (e.g. 
kaka-3184)?

Thanks. 

Reply via email to