Re: limiting the total number of documents matched

2010-07-16 Thread Yonik Seeley
On Wed, Jul 14, 2010 at 5:46 PM, Paul wrote: > I thought of another way to do it, but I still have one thing I don't > know how to do. I could do the search without sorting for the 50th > page, then look at the relevancy score on the first item on that page, > then repeat the search, but add score

Re: limiting the total number of documents matched

2010-07-16 Thread Lance Norskog
Yes, multiple (radix) sorts work and you can use the score value. The sort parameters come in order, most important to least important. This sorts first by score, and then documents with the same score are sorted by field f: sort=score+desc,f+asc On Wed, Jul 14, 2010 at 2:46 PM, Paul wrote: >

Re: limiting the total number of documents matched

2010-07-14 Thread Paul
I thought of another way to do it, but I still have one thing I don't know how to do. I could do the search without sorting for the 50th page, then look at the relevancy score on the first item on that page, then repeat the search, but add score > that relevancy as a parameter. Is it possible to do

Re: limiting the total number of documents matched

2010-07-14 Thread Paul
I was hoping for a way to do this purely by configuration and making the correct GET requests, but if there is a way to do it by creating a custom Request Handler, I suppose I could plunge into that. Would that yield the best results, and would that be particularly difficult? On Wed, Jul 14, 2010

RE: limiting the total number of documents matched

2010-07-14 Thread Nagelberg, Kallin
So you want to take the top 1000 sorted by score, then sort those by another field. It's a strange case, and I can't think of a clean way to accomplish it. You could do it in two queries, where the first is by score and you only request your IDs to keep it snappy, then do a second query against