Hi Bogunov!
Simple truncation of the bitcask files won't trigger this error, since
bitcask will notice that the last written entry is truncated and ignore
it. In this case a 'not found' is returned to the layer above bitcask.
If on the other hand, an entry (not necessarily the last one written
Oh, I forgot to mention:
My workaround was to patch riak_kv_bitcask_backend to map all errors to
{error,not_found}. Which begs the question if the 'get/3' function of
any backend should ever return anything other than
{ok, Value, State} and {error, not_found, State} if it isn't handled by
riak
