13 replies

Cursor based pagination on gremlin queries

I wanted to ask whether there's a way of implementing cursor based pagination on gremlin queries in a relatively performant way.
For example, if I were to run the following query:

g.V().hasLabel('person').order().by('created', asc)
     .limit(50)

g.V().hasLabel('person').order().by('created', asc)
     .limit(50)

, to get the first 50 results for all nodes with label "person" and ordered by the created attribute, and then save the highest created property for this batch of results, and then run

g.V().hasLabel('person').has('created', gt(last_highest_created_property).order().by('created', asc)
     .limit(50)

g.V().hasLabel('person').has('created', gt(last_highest_created_property).order().by('created', asc)
     .limit(50)

, would this effectively get me the next 50 results without having to traverse the first 50 again?

Apache TinkerPop•10mo ago•

13 replies

marti.sant

Cursor based pagination on gremlin queries

I wanted to ask whether there's a way of implementing cursor based pagination on gremlin queries in a relatively performant way.
For example, if I were to run the following query:

g.V().hasLabel('person').order().by('created', asc)
     .limit(50)

g.V().hasLabel('person').order().by('created', asc)
     .limit(50)

, to get the first 50 results for all nodes with label "person" and ordered by the created attribute, and then save the highest created property for this batch of results, and then run

g.V().hasLabel('person').has('created', gt(last_highest_created_property).order().by('created', asc)
     .limit(50)

g.V().hasLabel('person').has('created', gt(last_highest_created_property).order().by('created', asc)
     .limit(50)

, would this effectively get me the next 50 results without having to traverse the first 50 again?

Cursor based pagination on gremlin queries

Similar Threads

Cursor based pagination on gremlin queries

Similar Threads

Similar Threads

Similar Threads