bq. Does each write cause eviction of the cached block(s) Write first goes to memstore. If you read the same row immediately after write, the read request would be served by memstore - if flush hasn't happened.
On Fri, Mar 28, 2014 at 2:23 PM, Rendon, Carlos (KBB) <[email protected]>wrote: > Hi, > > If I have a workload where the access pattern is writing to and reading > from the same row, does it make sense to turn the blockcache off? In other > words, reads and writes to a given row always go together. Does each write > cause eviction of the cached block(s) that the row is stored in? I would > think so, but I couldn't find an answer to this anywhere online. > > Thanks, > Carlos >
