Hello Gordon, Any feedback? Did you get a chance to take a look at the cursor api prototype?
Thanks, Mike On Wed, Aug 30, 2017 at 6:00 PM, Mikhail Kebich <[email protected]> wrote: > On Wed, Aug 30, 2017 at 4:22 PM, gordon chung <[email protected]> wrote: >> ah, i see. iirc, we can choose what we sort on. can this be solved by >> just passing in a different sort key? or maybe we need to support >> returning results without sort. > > I thought about this. The key issue I see here is that the api does > not include "id" sort key to the result. Because of this api clients > can't specify a value of marker that points to the next batch of > events. And I believe we should think carefully about exposing this > filed because it may be meaningless depending on a storage back-end. > > Actually, cursors are intended to solve this issue by specifying a > value of marker explicitly without making an assumption what marker > is. > > I attached a prototype. It is based on stable/ocata branch. I did not > replace existing pagination and just provided another URL route to use > cursors. But, I think it is possible to replace current pagination > logic with cursors, because if a storage back-end understands markers > it can specify the value explicitly. > > Thanks, > Mike __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
