Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Paging #7

Open
narinearraul opened this issue Jan 29, 2017 · 2 comments
Open

Support Paging #7

narinearraul opened this issue Jan 29, 2017 · 2 comments
Assignees

Comments

@narinearraul
Copy link
Member

laik commented on Feb 25, 2016
As a user I would like to listen on a key and receive only a subset of values at a time.

Sorting needs to be determined.

@kevinlai
Copy link
Contributor

Introduce LVTS: LVTS guarantees everything later than itself up to RVTS has been synced.

LVTS and RVTS starts out the same, then as more historical data is needed, we make an advance call asking for n number of items before LVTS. LVTS is moved to the lowest VTS of the items returned.

Client SDKs are in charge of keeping track of LVTS/RVTS, and passing along the request for historical items.

@boopt2
Copy link
Contributor

boopt2 commented Apr 27, 2017

Due the scope of the implementation we have decided on, this will not be finished during this sprint

@boopt2 boopt2 removed this from the Release 1.4 milestone Apr 27, 2017
@boopt2 boopt2 added this to the Release 1.5 milestone May 16, 2017
@narinearraul narinearraul removed this from the Release 1.5 milestone May 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants