Re: Result order when score is the same

2011-04-13 Thread Otis Gospodnetic
r - Lucene - Nutch Lucene ecosystem search :: http://search-lucene.com/ - Original Message > From: kenf_nc > To: solr-user@lucene.apache.org > Sent: Wed, April 13, 2011 4:49:06 PM > Subject: Re: Result order when score is the same > > Is a new DocID generated everytime

Re: Result order when score is the same

2011-04-13 Thread Jonathan Rochkind
all documents. But, I would want the sort to be at the system level, I dont' want the overhead of sorting every query I ever make. How would 'doing it at the system level' avoid the 'overhead of sorting every query'? Every query has to be sorted, if you want it sorted. Beyond setting a def

Re: Result order when score is the same

2011-04-13 Thread Markus Jelsma
> Is a new DocID generated everytime a doc with the same UniqueID is added to > the index? If so, then docID must be incremental and would look like > indexed_at ascending. What I see (and why it's a problem for me) is the > following. Yes, Solr removes the old and inserts a new when updating an

Re: Result order when score is the same

2011-04-13 Thread kenf_nc
Is a new DocID generated everytime a doc with the same UniqueID is added to the index? If so, then docID must be incremental and would look like indexed_at ascending. What I see (and why it's a problem for me) is the following. a search brings back the first 5 documents in a result set of say 60.

Re: Result order when score is the same

2011-04-13 Thread Markus Jelsma
Sorting a large set is costly, the more fields you sort on, the more memory is consumed (and likely cached). If i remember correctly the result set will be ordered according to Lucene DocID's if there's nothing to sort on. If i read correctly, you don't want to specify those fixed sort paramete

Re: Result order when score is the same

2011-04-13 Thread Markus Jelsma
If you omitNorms and omitTermFreqAndPositions on the query field(s) and use no funky boost functions, all results will have identical score in AND-queries (or queries with one search term). IDF has no meaning because of AND, queryNorm is the same across the resultset, fieldNorm is 1 and TF is 1.

Re: Result order when score is the same

2011-04-13 Thread kenf_nc
Au contraire, I have almost 4 million documents, representing businesses in the US. And having the score be the same is a very common occurrence. It is quite clear from testing that if score is the same, then it sorts on indexed_at ascending. It seems silly to make me add a sort on every query, th

Re: Result order when score is the same

2011-04-13 Thread Jonathan Rochkind
In real life though, it seems unlikely that the relevancy score will ever be identical, so the second sort field will never be used. Is relevancy score ever identical? Rarely at any rate. On 4/13/2011 3:22 PM, Rob Casson wrote: you could just explicitly send multiple sorts...from the tutoria

Re: Result order when score is the same

2011-04-13 Thread Rob Casson
you could just explicitly send multiple sorts...from the tutorial: &sort=inStock asc, price desc cheers. On Wed, Apr 13, 2011 at 2:59 PM, kenf_nc wrote: > Is sort order when 'score' is the same a Lucene thing? Should I ask on the > Lucene forum? > > -- > View this message in context: > ht

Re: Result order when score is the same

2011-04-13 Thread kenf_nc
Is sort order when 'score' is the same a Lucene thing? Should I ask on the Lucene forum? -- View this message in context: http://lucene.472066.n3.nabble.com/Result-order-when-score-is-the-same-tp2816127p2817330.html Sent from the Solr - User mailing list archive at Nabble.com.