Re: Disabling solr scoring
Thanks Hoss got the point. Bhaumik Joshi From: Chris Hostetter <hossman_luc...@fucit.org> Sent: Friday, July 8, 2016 4:52 PM To: solr-user Subject: Re: Disabling solr scoring : Can you please elaborate? I am passing user defined sort field and order whenever i search. I think Mikhail just missunderstood your question -- he was giving an example of how to override the default sort (which uses score) with one that would ensure scores are not computed. : > Is there any way to completely disable scoring in solr cloud as i am : > always passing sort parameter whenever i search. In general, you don't have to do anythign special. Solr's internal code looks at the sort specified, and the fields requested (via the fl param) to determine if/when scores need to be computed while colleting documents. If scores aren't needed for any reason, then that info is passed down to the low level lucene document matching/collection code for optimizing the collection so scores aren't computed. -Hoss http://www.lucidworks.com/ Lucidworks<http://www.lucidworks.com/> www.lucidworks.com Lucidworks Fusion is the search and analytics platform powering the next generation of big data applications.
Re: Disabling solr scoring
: Can you please elaborate? I am passing user defined sort field and order whenever i search. I think Mikhail just missunderstood your question -- he was giving an example of how to override the default sort (which uses score) with one that would ensure scores are not computed. : > Is there any way to completely disable scoring in solr cloud as i am : > always passing sort parameter whenever i search. In general, you don't have to do anythign special. Solr's internal code looks at the sort specified, and the fields requested (via the fl param) to determine if/when scores need to be computed while colleting documents. If scores aren't needed for any reason, then that info is passed down to the low level lucene document matching/collection code for optimizing the collection so scores aren't computed. -Hoss http://www.lucidworks.com/
Re: Disabling solr scoring
Can you please elaborate? I am passing user defined sort field and order whenever i search. Thanks & Regards, Bhaumik Joshi From: Mikhail Khludnev <m...@apache.org> Sent: Friday, July 8, 2016 4:13 AM To: solr-user Subject: Re: Disabling solr scoring What about sort=_docid_ asc ? 08 2016 ?. 13:50 "Bhaumik Joshi" < bhaumik.jo...@outlook.com> ???: > Hi, > > > Is there any way to completely disable scoring in solr cloud as i am > always passing sort parameter whenever i search. > > And disabling scoring will improve performance? > > > Thanks & Regards, > > Bhaumik Joshi >
Re: Disabling solr scoring
What about sort=_docid_ asc ? 08 июля 2016 г. 13:50 пользователь "Bhaumik Joshi" < bhaumik.jo...@outlook.com> написал: > Hi, > > > Is there any way to completely disable scoring in solr cloud as i am > always passing sort parameter whenever i search. > > And disabling scoring will improve performance? > > > Thanks & Regards, > > Bhaumik Joshi >
Disabling solr scoring
Hi, Is there any way to completely disable scoring in solr cloud as i am always passing sort parameter whenever i search. And disabling scoring will improve performance? Thanks & Regards, Bhaumik Joshi
Solr scoring confusion
We are getting inconsistent scoring results in Solr. It works about 95% of the time, where a search on one term returns the results which equal exactly that one term at the top, and results with multiple terms that also contain that one term are returned lower. Occasionally, however, if a subset of the data has been re-indexed (the same data just added to the index again) then the results will be slightly off, for example the data from the earlier index will get a higher score than it should, until we re-index all the data. Our assumption here is that setting omitNorms to false, then indexing the data, then searching, should result in scores where the data with an exact match has a higher score. We usually see this but not always. Is something added to the score besides the value that is being searched that we are not understaning? Thanks. .. Scott Johnson Data Advantage Group, Inc. 604 Mission Street San Francisco, CA 94105 Office: +1.415.947.0400 x204 Fax: +1.415.947.0401 Take the first step towards a successful meta data initiative with MetaCenter - the only plug and play, real-time meta data solution.http://www.dag.com/ www.dag.com ..
Re: Solr scoring confusion
Hi Scott, Try optimizing after reindexing and this should go away. Had to do with updated/deleted docs participating in score computation. Otis On Feb 13, 2015, at 18:29, Scott Johnson sjohn...@dag.com wrote: We are getting inconsistent scoring results in Solr. It works about 95% of the time, where a search on one term returns the results which equal exactly that one term at the top, and results with multiple terms that also contain that one term are returned lower. Occasionally, however, if a subset of the data has been re-indexed (the same data just added to the index again) then the results will be slightly off, for example the data from the earlier index will get a higher score than it should, until we re-index all the data. Our assumption here is that setting omitNorms to false, then indexing the data, then searching, should result in scores where the data with an exact match has a higher score. We usually see this but not always. Is something added to the score besides the value that is being searched that we are not understaning? Thanks. .. Scott Johnson Data Advantage Group, Inc. 604 Mission Street San Francisco, CA 94105 Office: +1.415.947.0400 x204 Fax: +1.415.947.0401 Take the first step towards a successful meta data initiative with MetaCenter - the only plug and play, real-time meta data solution.http://www.dag.com/ www.dag.com ..
solr scoring
Hi All, I have a scenario where for example my document titles are 1. battle of the zords 2. joes battle 3. who was in that crazy battle. and if the search term is [battle] I want to penalize the second and third document score because battle was matched further down than in the first documents case. One way I can do this is store the title field and then retrieve the data at query time - compute the relative position of the token - and use it in my custom scorer. But this is not just extremely slow but also my index is huge. So I am planning to index payloads along with each token which will be some value relative to the term position in the original string. and then use the payload information along with any other scoring i have. Am I thinking on the right lines? is there anything better that i could do ? Thanks Summer
[ANN] vifun: a GUI to help visually tweak Solr scoring, release 0.6
Hi, I am releasing an new version (0.6) of vifun, a GUI to help visually tweak Solr scoring. Most relevant changes are: - support float values - add support for tie - synch both Current/Baseline scrollbars (if some checkbox is selected) - doubleclick in a doc: show side by side comparison of debug score info - upgrade to griffon1.2.0 - allow using another handler (besides /select) enhancement You can check it out here: https://github.com/jmlucjav/vifun Binary distribution: http://code.google.com/p/vifun/downloads/detail?name=vifun-0.6.zip xavier
Re: Solr Scoring
This was a common one when I was matching movie and song names. If that is your project, also try boosting if it's the first word or on shorter titles. Also try bigrams of stopwords: Call of the Wild becomes call, of-the, wild. The bigrams trick is also good if you have people block-copying large chunks of boilerplate for finding official documents. On Fri, Apr 13, 2012 at 2:04 AM, Kissue Kissue kissue...@gmail.com wrote: Thanks a lot. I had already implemented Walter's solution and was wondering if this was the right way to deal with it. This has now given me the confidence to go with the solution. Many thanks. On Fri, Apr 13, 2012 at 1:04 AM, Erick Erickson erickerick...@gmail.comwrote: GAH! I had my head in make this happen in one field when I wrote my response, without being explicit. Of course Walter's solution is pretty much the standard way to deal with this. Best Erick On Thu, Apr 12, 2012 at 5:38 PM, Walter Underwood wun...@wunderwood.org wrote: It is easy. Create two fields, text_exact and text_stem. Don't use the stemmer in the first chain, do use the stemmer in the second. Give the text_exact a bigger weight than text_stem. wunder On Apr 12, 2012, at 4:34 PM, Erick Erickson wrote: No, I don't think there's an OOB way to make this happen. It's a recurring theme, make exact matches score higher than stemmed matches. Best Erick On Thu, Apr 12, 2012 at 5:18 AM, Kissue Kissue kissue...@gmail.com wrote: Hi, I have a field in my index called itemDesc which i am applying EnglishMinimalStemFilterFactory to. So if i index a value to this field containing Edges, the EnglishMinimalStemFilterFactory applies stemming and Edges becomes Edge. Now when i search for Edges, documents with Edge score better than documents with the actual search word - Edges. Is there a way i can make documents with the actual search word in this case Edges score better than document with Edge? I am using Solr 3.5. My field definition is shown below: fieldType name=text_en class=solr.TextField positionIncrementGap=100 analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=index_synonyms.txt ignoreCase=true expand=false/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer analyzer type=query tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=synonyms.txt ignoreCase=true expand=true/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true / filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.KeywordMarkerFilterFactory protected=protwords.txt/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer /fieldType Thanks. -- Lance Norskog goks...@gmail.com
Re: Solr Scoring
another way is to use payload http://wiki.apache.org/solr/Payloads the advantage of payload is that you only need one field and can make frq file smaller than use two fields. but the disadvantage is payload is stored in prx file, so I am not sure which one is fast. maybe you can try them both. On Fri, Apr 13, 2012 at 8:04 AM, Erick Erickson erickerick...@gmail.comwrote: GAH! I had my head in make this happen in one field when I wrote my response, without being explicit. Of course Walter's solution is pretty much the standard way to deal with this. Best Erick On Thu, Apr 12, 2012 at 5:38 PM, Walter Underwood wun...@wunderwood.org wrote: It is easy. Create two fields, text_exact and text_stem. Don't use the stemmer in the first chain, do use the stemmer in the second. Give the text_exact a bigger weight than text_stem. wunder On Apr 12, 2012, at 4:34 PM, Erick Erickson wrote: No, I don't think there's an OOB way to make this happen. It's a recurring theme, make exact matches score higher than stemmed matches. Best Erick On Thu, Apr 12, 2012 at 5:18 AM, Kissue Kissue kissue...@gmail.com wrote: Hi, I have a field in my index called itemDesc which i am applying EnglishMinimalStemFilterFactory to. So if i index a value to this field containing Edges, the EnglishMinimalStemFilterFactory applies stemming and Edges becomes Edge. Now when i search for Edges, documents with Edge score better than documents with the actual search word - Edges. Is there a way i can make documents with the actual search word in this case Edges score better than document with Edge? I am using Solr 3.5. My field definition is shown below: fieldType name=text_en class=solr.TextField positionIncrementGap=100 analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=index_synonyms.txt ignoreCase=true expand=false/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer analyzer type=query tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=synonyms.txt ignoreCase=true expand=true/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true / filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.KeywordMarkerFilterFactory protected=protwords.txt/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer /fieldType Thanks.
Re: Solr Scoring
Thanks a lot. I had already implemented Walter's solution and was wondering if this was the right way to deal with it. This has now given me the confidence to go with the solution. Many thanks. On Fri, Apr 13, 2012 at 1:04 AM, Erick Erickson erickerick...@gmail.comwrote: GAH! I had my head in make this happen in one field when I wrote my response, without being explicit. Of course Walter's solution is pretty much the standard way to deal with this. Best Erick On Thu, Apr 12, 2012 at 5:38 PM, Walter Underwood wun...@wunderwood.org wrote: It is easy. Create two fields, text_exact and text_stem. Don't use the stemmer in the first chain, do use the stemmer in the second. Give the text_exact a bigger weight than text_stem. wunder On Apr 12, 2012, at 4:34 PM, Erick Erickson wrote: No, I don't think there's an OOB way to make this happen. It's a recurring theme, make exact matches score higher than stemmed matches. Best Erick On Thu, Apr 12, 2012 at 5:18 AM, Kissue Kissue kissue...@gmail.com wrote: Hi, I have a field in my index called itemDesc which i am applying EnglishMinimalStemFilterFactory to. So if i index a value to this field containing Edges, the EnglishMinimalStemFilterFactory applies stemming and Edges becomes Edge. Now when i search for Edges, documents with Edge score better than documents with the actual search word - Edges. Is there a way i can make documents with the actual search word in this case Edges score better than document with Edge? I am using Solr 3.5. My field definition is shown below: fieldType name=text_en class=solr.TextField positionIncrementGap=100 analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=index_synonyms.txt ignoreCase=true expand=false/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer analyzer type=query tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=synonyms.txt ignoreCase=true expand=true/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true / filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.KeywordMarkerFilterFactory protected=protwords.txt/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer /fieldType Thanks.
Solr Scoring
Hi, I have a field in my index called itemDesc which i am applying EnglishMinimalStemFilterFactory to. So if i index a value to this field containing Edges, the EnglishMinimalStemFilterFactory applies stemming and Edges becomes Edge. Now when i search for Edges, documents with Edge score better than documents with the actual search word - Edges. Is there a way i can make documents with the actual search word in this case Edges score better than document with Edge? I am using Solr 3.5. My field definition is shown below: fieldType name=text_en class=solr.TextField positionIncrementGap=100 analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=index_synonyms.txt ignoreCase=true expand=false/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer analyzer type=query tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=synonyms.txt ignoreCase=true expand=true/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true / filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.KeywordMarkerFilterFactory protected=protwords.txt/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer /fieldType Thanks.
Re: Solr Scoring
No, I don't think there's an OOB way to make this happen. It's a recurring theme, make exact matches score higher than stemmed matches. Best Erick On Thu, Apr 12, 2012 at 5:18 AM, Kissue Kissue kissue...@gmail.com wrote: Hi, I have a field in my index called itemDesc which i am applying EnglishMinimalStemFilterFactory to. So if i index a value to this field containing Edges, the EnglishMinimalStemFilterFactory applies stemming and Edges becomes Edge. Now when i search for Edges, documents with Edge score better than documents with the actual search word - Edges. Is there a way i can make documents with the actual search word in this case Edges score better than document with Edge? I am using Solr 3.5. My field definition is shown below: fieldType name=text_en class=solr.TextField positionIncrementGap=100 analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=index_synonyms.txt ignoreCase=true expand=false/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer analyzer type=query tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=synonyms.txt ignoreCase=true expand=true/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true / filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.KeywordMarkerFilterFactory protected=protwords.txt/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer /fieldType Thanks.
Re: Solr Scoring
It is easy. Create two fields, text_exact and text_stem. Don't use the stemmer in the first chain, do use the stemmer in the second. Give the text_exact a bigger weight than text_stem. wunder On Apr 12, 2012, at 4:34 PM, Erick Erickson wrote: No, I don't think there's an OOB way to make this happen. It's a recurring theme, make exact matches score higher than stemmed matches. Best Erick On Thu, Apr 12, 2012 at 5:18 AM, Kissue Kissue kissue...@gmail.com wrote: Hi, I have a field in my index called itemDesc which i am applying EnglishMinimalStemFilterFactory to. So if i index a value to this field containing Edges, the EnglishMinimalStemFilterFactory applies stemming and Edges becomes Edge. Now when i search for Edges, documents with Edge score better than documents with the actual search word - Edges. Is there a way i can make documents with the actual search word in this case Edges score better than document with Edge? I am using Solr 3.5. My field definition is shown below: fieldType name=text_en class=solr.TextField positionIncrementGap=100 analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=index_synonyms.txt ignoreCase=true expand=false/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer analyzer type=query tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=synonyms.txt ignoreCase=true expand=true/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true / filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.KeywordMarkerFilterFactory protected=protwords.txt/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer /fieldType Thanks.
Re: Solr Scoring
GAH! I had my head in make this happen in one field when I wrote my response, without being explicit. Of course Walter's solution is pretty much the standard way to deal with this. Best Erick On Thu, Apr 12, 2012 at 5:38 PM, Walter Underwood wun...@wunderwood.org wrote: It is easy. Create two fields, text_exact and text_stem. Don't use the stemmer in the first chain, do use the stemmer in the second. Give the text_exact a bigger weight than text_stem. wunder On Apr 12, 2012, at 4:34 PM, Erick Erickson wrote: No, I don't think there's an OOB way to make this happen. It's a recurring theme, make exact matches score higher than stemmed matches. Best Erick On Thu, Apr 12, 2012 at 5:18 AM, Kissue Kissue kissue...@gmail.com wrote: Hi, I have a field in my index called itemDesc which i am applying EnglishMinimalStemFilterFactory to. So if i index a value to this field containing Edges, the EnglishMinimalStemFilterFactory applies stemming and Edges becomes Edge. Now when i search for Edges, documents with Edge score better than documents with the actual search word - Edges. Is there a way i can make documents with the actual search word in this case Edges score better than document with Edge? I am using Solr 3.5. My field definition is shown below: fieldType name=text_en class=solr.TextField positionIncrementGap=100 analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=index_synonyms.txt ignoreCase=true expand=false/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer analyzer type=query tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.SynonymFilterFactory synonyms=synonyms.txt ignoreCase=true expand=true/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords_en.txt enablePositionIncrements=true / filter class=solr.LowerCaseFilterFactory/ filter class=solr.EnglishPossessiveFilterFactory/ filter class=solr.KeywordMarkerFilterFactory protected=protwords.txt/ filter class=solr.EnglishMinimalStemFilterFactory/ /analyzer /fieldType Thanks.
Re: Solr Scoring question
filter queries (fq) are not included for score calculation, just the query in q parameter is used for this purpose. That's why although you get the same results, lucene will just use q=*:* in your 1st query and q=tag:car in your 2nd query to calculate the scores. As you can see since both queries are different you should expect different scores. If you want the details about how the score is calculated for each doc, append debugQuery=true to your Solr's query string and check the explain section On Thu, Jan 5, 2012 at 6:16 PM, Simon Willnauer simon.willna...@googlemail.com wrote: hey, On Thu, Jan 5, 2012 at 9:31 PM, Christopher Gross cogr...@gmail.com wrote: I'm getting different results running these queries: http://localhost:8080/solr/select?q=*:*fq=source:wikifq=tag:carsort=score+desc,dateSubmitted+ascfl=title,score,dateSubmittedrows=100 http://localhost:8080/solr/select?fq=source:wikiq=tag:carsort=score+desc,dateSubmitted+descfl=title,score,dateSubmittedrows=100 They return the same amount of results (and I'm assuming the same ones) -- but the first one (with q=*:*) has a score of 1 for all results, making it only sort by dateSubmitted. The second one has scores, and it properly sorts them. I was thinking that the two would be equivalent and give the same results in the same order, but I'm guessing that there is something happening behind the scenes in Solr (Lucene?) that makes the *:* give me a score of 1.0 for everything. I tried to find some documentation to figure out if this is the case, but I'm not having much luck for that. q=*:* is a constant score query that retireves all documents in your index. The issue here is that with *:* you don't have anything to score while with q=tag:car you can score the term car with tf idf etc. does that make sense? simon I have a JSP file that will take in parameters, do some work on them to make them appropriate for Solr, then pass the query it builds to Solr. Should I just put more brains in that to avoid using a *:* (we're trying to verify results and we ran into this oddity). This is for Solr 3.4, running Tomcat 5.5.25 on Java 1.5. Thanks! Let me know if Ineed to clarify anything... -- Chris
Solr Scoring question
I'm getting different results running these queries: http://localhost:8080/solr/select?q=*:*fq=source:wikifq=tag:carsort=score+desc,dateSubmitted+ascfl=title,score,dateSubmittedrows=100 http://localhost:8080/solr/select?fq=source:wikiq=tag:carsort=score+desc,dateSubmitted+descfl=title,score,dateSubmittedrows=100 They return the same amount of results (and I'm assuming the same ones) -- but the first one (with q=*:*) has a score of 1 for all results, making it only sort by dateSubmitted. The second one has scores, and it properly sorts them. I was thinking that the two would be equivalent and give the same results in the same order, but I'm guessing that there is something happening behind the scenes in Solr (Lucene?) that makes the *:* give me a score of 1.0 for everything. I tried to find some documentation to figure out if this is the case, but I'm not having much luck for that. I have a JSP file that will take in parameters, do some work on them to make them appropriate for Solr, then pass the query it builds to Solr. Should I just put more brains in that to avoid using a *:* (we're trying to verify results and we ran into this oddity). This is for Solr 3.4, running Tomcat 5.5.25 on Java 1.5. Thanks! Let me know if Ineed to clarify anything... -- Chris
Re: Solr Scoring question
hey, On Thu, Jan 5, 2012 at 9:31 PM, Christopher Gross cogr...@gmail.com wrote: I'm getting different results running these queries: http://localhost:8080/solr/select?q=*:*fq=source:wikifq=tag:carsort=score+desc,dateSubmitted+ascfl=title,score,dateSubmittedrows=100 http://localhost:8080/solr/select?fq=source:wikiq=tag:carsort=score+desc,dateSubmitted+descfl=title,score,dateSubmittedrows=100 They return the same amount of results (and I'm assuming the same ones) -- but the first one (with q=*:*) has a score of 1 for all results, making it only sort by dateSubmitted. The second one has scores, and it properly sorts them. I was thinking that the two would be equivalent and give the same results in the same order, but I'm guessing that there is something happening behind the scenes in Solr (Lucene?) that makes the *:* give me a score of 1.0 for everything. I tried to find some documentation to figure out if this is the case, but I'm not having much luck for that. q=*:* is a constant score query that retireves all documents in your index. The issue here is that with *:* you don't have anything to score while with q=tag:car you can score the term car with tf idf etc. does that make sense? simon I have a JSP file that will take in parameters, do some work on them to make them appropriate for Solr, then pass the query it builds to Solr. Should I just put more brains in that to avoid using a *:* (we're trying to verify results and we ran into this oddity). This is for Solr 3.4, running Tomcat 5.5.25 on Java 1.5. Thanks! Let me know if Ineed to clarify anything... -- Chris
modify SOLR scoring
Hi everybody, I'm using SOLR with a schema (for example) like this: parutiondate, date, indexed, not stored fulltext, stemmed, indexed, not stored I know it's possible to order by a field or more, but I want to order by score and modify the scrore formula. I'll want keep the SOLR score but add a new parameter in the formula to boost the score of the most recent document. What is the best way to do this ? Thanks. Excuse for my english. -- View this message in context: http://www.nabble.com/modify-SOLR-scoring-tp23198326p23198326.html Sent from the Solr - User mailing list archive at Nabble.com.
RE: modify SOLR scoring
I believe you can use a function query to do this: http://wiki.apache.org/solr/FunctionQuery if you embed the following in your query, you should get a boost for more recent date values: _val_:ord(dateField) Where dateField is the field name of the date you want to use. -Original Message- From: Bertrand DUMAS-PILHOU [mailto:bdum...@eurocortex.fr] Sent: Thursday, April 23, 2009 3:44 PM To: solr-user@lucene.apache.org Subject: modify SOLR scoring Hi everybody, I'm using SOLR with a schema (for example) like this: parutiondate, date, indexed, not stored fulltext, stemmed, indexed, not stored I know it's possible to order by a field or more, but I want to order by score and modify the scrore formula. I'll want keep the SOLR score but add a new parameter in the formula to boost the score of the most recent document. What is the best way to do this ? Thanks. Excuse for my english. -- View this message in context: http://www.nabble.com/modify-SOLR- scoring-tp23198326p23198326.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: modify SOLR scoring
Hi. I am interested in a very similar topic like yours. I want to modify the field named score and the document boost but not reindex the all fields since it would take to much power. Please let me know if you find a solution to this. Kindly //Marcus On Thu, Apr 23, 2009 at 10:02 PM, Ensdorf Ken ensd...@zoominfo.com wrote: I believe you can use a function query to do this: http://wiki.apache.org/solr/FunctionQuery if you embed the following in your query, you should get a boost for more recent date values: _val_:ord(dateField) Where dateField is the field name of the date you want to use. -Original Message- From: Bertrand DUMAS-PILHOU [mailto:bdum...@eurocortex.fr] Sent: Thursday, April 23, 2009 3:44 PM To: solr-user@lucene.apache.org Subject: modify SOLR scoring Hi everybody, I'm using SOLR with a schema (for example) like this: parutiondate, date, indexed, not stored fulltext, stemmed, indexed, not stored I know it's possible to order by a field or more, but I want to order by score and modify the scrore formula. I'll want keep the SOLR score but add a new parameter in the formula to boost the score of the most recent document. What is the best way to do this ? Thanks. Excuse for my english. -- View this message in context: http://www.nabble.com/modify-SOLR- scoring-tp23198326p23198326.html Sent from the Solr - User mailing list archive at Nabble.com. -- Marcus Herou CTO and co-founder Tailsweep AB +46702561312 marcus.he...@tailsweep.com http://www.tailsweep.com/ http://blogg.tailsweep.com/
Solr scoring: relative or absolute?
Are the score values generated in Solr relative to the index or are they against an absolute standard? Is it possible to create a scoring algorithm with this property? Are there parts of the score inputs that are absolute? My use case is this: I would like to do a parallel search against two Solr indexes, and combine the results. The two indexes are built with the same data sources, we just can't handle one giant index. If the score values are against a common 'scale', then scores from the two search indexes can be compared. I could combine the result sets with a simple merge by score. This is a difficult concept to explain. I hope I have succeeded. Thanks, Lance
Re: Solr scoring: relative or absolute?
Indexes cannot be directly compared unless they have similar collection statistics. That is the same terms occur with the same frequency across all indexes and the average document lengths are about the same (though the default similarity in Lucene may not care about average document length--I'm not sure). SOLR-303 is an attempt to solve the partitioning issue from the search side of things. -Sean Lance Norskog wrote: Are the score values generated in Solr relative to the index or are they against an absolute standard? Is it possible to create a scoring algorithm with this property? Are there parts of the score inputs that are absolute? My use case is this: I would like to do a parallel search against two Solr indexes, and combine the results. The two indexes are built with the same data sources, we just can't handle one giant index. If the score values are against a common 'scale', then scores from the two search indexes can be compared. I could combine the result sets with a simple merge by score. This is a difficult concept to explain. I hope I have succeeded. Thanks, Lance
