Should we add support for fetcher/stream that fetches by range rather than key? about store

[yigit]

lets keep it open, at least for now. Paging 3 is about to do an EAP that'll help us better finalize the APIs. I have a demo app where i'm trying to integrate both but last time i tried, the added value was none.
I just don't want to pre-maturely close this one w/ o a final decision or at least a sample that shows why we won't do integration.
i'll assign it to me.

[yigit]

i'm waiting for paging3 API to become more mature to start tackling this. It'll soon be EAP where we should have a better idea where everything fits.

Paging does similar things store do (sharing). It might be mostly letting people return PagedData.share() instances from store for one part.
For the data source of the paging, it might make sense to put store behind as well.

My plan is to first hand write it to see how it would look and then see if we have some ways to make it more smooth.
I don't think we'll need to add range as it won't be much different than a composite key. But again, this requires a lot more tinkering w/ before saying something proper.

[digitalbuddha]

@yigit you mentioned not much to gain with store/paging. Is that still the case? Should be close this?

[digitalbuddha]

paging is out, I don't see any gain from a paging store. Closing