Hey Ben,
Cool, please email if anything else comes up. Re: fresh-store, I think it
should be possible to add a .clear() to the KV interface. This would result
in creating a new DB and deleting the old one. Like the RocksDB TTL, it
wouldn't result in any deletes being sent to the changelog, though.
I think having followed along with the other thread, my initial approach
was flawed. We use Cassandra in prod a ton (the classic Cassandra / Spark
combo) at my job and have been running into a few issues with streaming /
local state etc etc. Hence my wanting to have a look at Samza. Very long
way r
Hey Ben,
The problem with TTL is that it's handled entirely internally in RocksDB.
There's no way for us to know when a key's been deleted. You can work
around this if you also alter the changelog topic settings in your
changelog Kafka topic to be TTL based, not log-compacted, then these two
shoul
Yes, I was using a changelog. You bring up a good point. I think I need to
think harder about what I am trying to do. Maybe deleting all the keys
isn't that bad. Especially is I amortise it over the life of the next
period.
It seems like waiting for TTLs is probably the right thing to do ultimatel
Hey Benjamin,
You're right. Currently you have to call .all(), and delete everything.
RocksDB just committed TTL support for their Java library. This feature
allows data to automatically be expired out. Once RocksDB releases their
TTL patch (I believe in a few weeks, according to Igor), we'll upd
