samza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Riccomini <>
Subject Re: Stream-Stream joins - restricting the size of the KV store
Date Tue, 03 Mar 2015 18:32:02 GMT
Hey Kishore,

Right now, that has to be done by the application code. Our plan is to
support a TTL in RocksDB once that feature is available to us in the Java
JNI bindings (should be soon). In the meantime, you'll have to implement
the WindowableTask.window() method, and call store.all() to periodically
clear out old keys.


On Tue, Mar 3, 2015 at 9:08 AM, Kishore N C <> wrote:

> Hi all,
> I just read through this post
> <
> >
> about implementing streaming joins in Samza using a KV store that Samza
> provides. Can someone tell me how I can ensure that this KV storage does
> not grow too large (even though I know that this is on disk)? Does Samza
> provide a way to purge older keys, or is that expected to be done by the
> application code?
> Thanks.
> KN.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message