And there's a tiny test in
https://github.com/neo4j/community/blob/master/kernel/src/test/java/org/neo4j/helpers/collection/TestCommonIterators.java#L146
2011/7/30 Jim Webber j...@neotechnology.com
There's JavaDoc here:
The PagingIterator caches the results lazily going forward with the ability
to go back through the pages. Going forward again will return cached values
as far as possible and then go down to the real iterator again when the end
of the cache is reached. So it will not cache the entire result up
. Yes I know I can test this but
I need to be sure if this will work every time not only for my few tests. My
question is how this result is sorted by default.
--
View this message in context:
http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-Pagination-in-Embedded-tp3202018p3209605
Now that is interesting - I hadn't considered this when writing the REST paging
stuff.
When you say that the PagingIterator caches, what's the memory overhead
involved, particularly when I want to page backwards through a potentially
large result set?
Jim
Is there any example of using PagingIterator? Thanks
--
View this message in context:
http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-Pagination-in-Embedded-tp3202018p3210956.html
Sent from the Neo4j Community Discussions mailing list archive at Nabble.com
Hi John,
In an embedded scenario, pagination doesn't make as much sense. Since calls to
the embedded APIs typically return a lazily-evaluatable iterableT you just
call next() to efficiently advance through the results.
Jim
___
Neo4j mailing list
implementation of neo4j would be better in this scenario?
Thanks.
T
--
View this message in context:
http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-Pagination-in-Embedded-tp3202018p3203156.html
Sent from the Neo4j Community Discussions mailing list archive at Nabble.com
Looks like John H. means, how do you get all results for page N and only for
page N ? without the overhead of getting thru all other results; so far, as
I understand it (also from what Jim said), you'll have to parse all the
results for all pages prior to page N, to get to page N, but not the
My scenario is: If there 1000 results from an index query, I would like to
send 100 at a time to the requesting client(ie, browser).
Which means browser will make 10 calls to get all the results by passing
either the page number or the next start result(ie, 11, 21, 31 etc) in each
call.
It looks
Hi John,
OK, gotcha. I didn't realise there's a network hop in there too.
Go ahead on use the PagingIterator.
Jim
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
Hello,
Is there an example or documentation on how to achieve pagination when using
the embedded version?
Typically, if there are large search results from an index query we would
like to paginate these results across multiple browser requests.
TIA,
John
11 matches
Mail list logo
