Hi Michael, The short answer is I'd like to see paging for traversals as well. I have considered using traversals instead of an index for following reasons: 1) To see if it's faster and 2) to give the user results closer to their own node. I.e. they would see names from those who are 2 or 3 degrees from them rather than the first 4 results from the entire database. Just haven't had time yet to try it.
My priority for paging support would be whichever can give me the quickest results over my data set, and I'm not sure if that is going to be traversals or an index. I have 2m nodes indexed, with 2 indexes total. One exact index for a unique ID and one fulltext for full name, first name, and last name. I will most likely eliminate the first name and last name fields. No relationship indexes. Not sure about the data volume, but we generally have a dozen people using the app at a time. Todd > ------------------------------ > > Message: 5 > Date: Wed, 27 Apr 2011 08:08:16 +0200 > From: Michael Hunger <[email protected]> > Subject: Re: [Neo4j] Paging of REST results > To: Neo4j user discussions <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > Todd, > > thanks for providing the use-case. > > So you need paging only for index query results, not for traversals? > > What is your data volume, how many nodes and different fields do you have > indexed and is there a > index per field or a global one? > > Cheers > > Michael > > Am 26.04.2011 um 22:54 schrieb Todd Chaffee: > > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
