On 04.03.2019 19:14, Matthias J. Sax wrote: > Thanks Adam, > > *> Q) Range scans work with caching enabled, too. Thus, there is no > functional/correctness requirement to disable caching. I cannot > remember why Jan's proposal added this? It might be an > implementation detail though (maybe just remove it from the KIP? > -- might be miss leading).
I dont know how to range scan over a caching store, probably one had to open 2 iterators and merge them. Other than that, I still think even the regualr join is broken with caching enabled right? I once files a ticket, because with caching enabled it would return values that havent been published downstream yet.
