Re: Disabling Lucene Scoring/Ranking

fwiw https://issues.apache.org/jira/browse/LUCENE-5867 is going to be released soon. On Mon, Jan 9, 2017 at 2:17 PM, Rajnish kamboj wrote: > My application does not require scoring/ranking. All data is equally > important for me. > > Search query can return any

Re: Disabling Lucene Scoring/Ranking

Thanks for quick responses.. I will try the approach.. Does bypassing scoring increases search performance also? Regards Rajnish On Monday, January 9, 2017, Ian Lea wrote: > oal.search.ConstantScoreQuery? > > "A query that wraps another query and simply returns a constant

Re: Disabling Lucene Scoring/Ranking

oal.search.ConstantScoreQuery? "A query that wraps another query and simply returns a constant score equal to the query boost for every document that matches the query. It therefore simply strips of all scores and returns a constant one." -- Ian. On Mon, Jan 9, 2017 at 11:39 AM, Taher Galal

Re: Disabling Lucene Scoring/Ranking

Just wrap your Query in a ConstantScoreQuery. Lucene will optimize the query execution to not read term frequencies from disk, not compute scores, etc. Mike McCandless http://blog.mikemccandless.com On Mon, Jan 9, 2017 at 6:17 AM, Rajnish kamboj wrote: > My

Re: Disabling Lucene Scoring/Ranking

Hi, What about writing your own scoring that just give a value of 1 to all the documents that are hits? On Mon, Jan 9, 2017 at 12:17 PM, Rajnish kamboj wrote: > My application does not require scoring/ranking. All data is equally > important for me. > > Search query

Disabling Lucene Scoring/Ranking

My application does not require scoring/ranking. All data is equally important for me. Search query can return any documents matching search criteria. So, Is there a way to completely disable scoring/ranking altogether? OR Is there a better solution to it. Regards Rajnish

Re: CPU usage 100% during search

We being new to Lucene are struggling hard to dimension our application w.r.t search throughput As stated by "Mike McCandless" in the following thread, we had ran our cases with restrictive data set also.