It's runner dependent. Some runners (e.g. the Dataflow runner) do have such a cache, though I think it's currently has a cap for large bags.
Reuven On Mon, Jul 15, 2019 at 8:48 PM Rakesh Kumar <rakeshku...@lyft.com> wrote: > Hi, > > I have been using python sdk for the application and also using BagState > in production. I was wondering whether state logic has any > write-through-cache implemented or not. If we are sending every read and > write request through network then it comes with a performance cost. We can > avoid network call for a read operation if we have write-through-cache. > I have superficially looked into the implementation and I didn't see any > cache implementation. > > is it possible to have this cache? would it cause any issue if we have the > caching layer? > >
