Re: Strange behavior of edismax and mm=0 with long queries (bug?)

2014-04-06 Thread Nils Kaiser
the query is much longer. I need to use mm=0 or mm=1. My plan was to use edismax as the pf2 and pf3 parameters should work well for my usecase. However when using longer queries, I get a strange behavior which can be seen in debugQuery. Here is an example: Collated Comments (used as query) I

Re: Strange behavior of edismax and mm=0 with long queries (bug?)

2014-04-05 Thread Jack Krupansky
query term phrase matches exactly. -- Jack Krupansky From: Nils Kaiser Sent: Friday, April 4, 2014 10:10 AM To: solr-user@lucene.apache.org Subject: Strange behavior of edismax and mm=0 with long queries (bug?) Hey, I am currently using solr to recognize songs and people from a list of user

Strange behavior of edismax and mm=0 with long queries (bug?)

2014-04-04 Thread Nils Kaiser
the collated comments as query. So it is a case where the query is much longer. I need to use mm=0 or mm=1. My plan was to use edismax as the pf2 and pf3 parameters should work well for my usecase. However when using longer queries, I get a strange behavior which can be seen in debugQuery. Here

Re: mm=0?

2010-09-13 Thread Jan Høydahl / Cominvent
As Erick points out, you don't want a random doc as response! What you're looking at is how to avoid the 0 hits problem. You could look into one of these: * Introduce autosuggest to avoid many 0-hits cases * Introduce spellchecking * Re-run the failed query with fuzzy turned on (e.g. alpha~) *

Re: mm=0?

2010-09-13 Thread Satish Kumar
Hi Erik, I completely agree with you that showing a random document for user's query would be very poor experience. I have raised this in our product review meetings before. I was told that because of contractual agreement some sponsored content needs to be returned even if it meant no match. And

Re: mm=0?

2010-09-13 Thread Dennis Gearon
...@gmail.com Subject: Re: mm=0? To: solr-user@lucene.apache.org Date: Monday, September 13, 2010, 7:41 AM Hi Erik, I completely agree with you that showing a random document for user's query would be very poor experience. I have raised this in our product review meetings before. I was told

Re: mm=0?

2010-09-13 Thread Dennis Gearon
wrote: From: Satish Kumar satish.kumar.just.d...@gmail.com Subject: Re: mm=0? To: solr-user@lucene.apache.org Date: Monday, September 13, 2010, 7:41 AM Hi Erik, I completely agree with you that showing a random document for user's query would be very poor experience. I have raised

Re: mm=0?

2010-09-13 Thread Lance Norskog
. Read 'Hot, Flat, and Crowded' Laugh at http://www.yert.com/film.php --- On Mon, 9/13/10, Satish Kumar satish.kumar.just.d...@gmail.com wrote: From: Satish Kumar satish.kumar.just.d...@gmail.com Subject: Re: mm=0? To: solr-user@lucene.apache.org Date: Monday, September 13, 2010, 7:41 AM Hi

Re: mm=0?

2010-09-13 Thread Simon Willnauer
Kumar satish.kumar.just.d...@gmail.com Subject: Re: mm=0? To: solr-user@lucene.apache.org Date: Monday, September 13, 2010, 7:41 AM Hi Erik, I completely agree with you that showing a random document for user's query would be very poor experience. I have raised this in our product review

Re: mm=0?

2010-09-12 Thread Erick Erickson
Could you explain the use-case a bit? Because the very first response I would have is why in the world did product management make this a requirement and try to get the requirement changed As a user, I'm having a hard time imagining being well served by getting a document in response to a

mm=0?

2010-09-11 Thread Satish Kumar
Hi, We have a requirement to show at least one result every time -- i.e., even if user entered term is not found in any of the documents. I was hoping setting mm to 0 will return results in all cases, but it is not. For example, if user entered term alpha and it is *not* in any of the documents