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

Paginate task listing #12

Open
ghost opened this issue Sep 4, 2013 · 4 comments
Open

Paginate task listing #12

ghost opened this issue Sep 4, 2013 · 4 comments

Comments

@ghost
Copy link

ghost commented Sep 4, 2013

Task listing should take limit and greater-than some-id constraints.

@danielcompton
Copy link
Contributor

Do you also want a next command? Maintaining the state between requests might not be desirable though.

@aphyr
Copy link
Contributor

aphyr commented Nov 10, 2014

Naw, I think it's fine to drop some ops. Best-estimate instead of correctness is critical for this performing well, haha. Traversing backwards in time should be relatively stable anyway.

@danielcompton
Copy link
Contributor

So each pagination request is separate with no shared state? Do we want a less than id param if we're traversing backwards?

@aphyr
Copy link
Contributor

aphyr commented Nov 10, 2014

Yeah, I'd say less than and greater-than are reasonable. There's probably an extended discussion to happen around the sort-merge equi-join and how much estimation is acceptable. My guess is it's probably ideal to estimate a range based on density then return every result with an ID between a lower and upper ID bound, rather than doing a hard-limit and throwing away a bunch of IDs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants