> On May 10, 2018, at 10:48 AM, Steven Schlansker <sschlans...@opentable.com> > wrote: > > But it still remains -- when you go an read that ROKVS documentation, it sure > doesn't prepare you to this possibility! And, it's a little frustrating that > we have to have this 'caching' layer at all -- we already had to add > > // ensure KTable doesn't delay updates due to buffering in cache > kafkaStreamProps.put(StreamsConfig.CACHE_MAX_BYTES_BUFFERING_CONFIG, > 0);
Now that I've said this, it seems that since I last checked we got 'Materialized.withCachingDisabled'. I'll see if that does what I want... (I still think the docs and CachingKVS behavior could improve, though.)
signature.asc
Description: Message signed with OpenPGP using GPGMail
