Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Mon, 24 Nov 2008 15:40:29 -0800 (PST)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: solr-user@lucene.apache.org
Subject: Re: Please Help !! Question about Query Phrase Slop (qs) in dismax
In-Reply-To: <20654906.post@talk.nabble.com>
Message-ID: <Pine.LNX.4.62.0811241529540.25100@radix.cryptio.net>
References: <20643003.post@talk.nabble.com> <20654906.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: Subject: Re: Please Help !! Question about Query Phrase Slop (qs) in dismax
: 
: 
: Please help someone...i've been waiting for an answer for the last couple of
: days & no one seems to be helping out here. I did search the wiki & this

Please don't send messages like this.  

This is a volunteer community -- no one (that I know of) is paid to 
read/reply to questions on the solr-user list.  Many of us do our best to 
make sure that all user questions get addressed, but this is a fairly high 
volume list, and sometimes other things in life (work, health, 
relationships, family, etc...) make that take a little longer then we 
would like -- sometimes questions don't get answered for a few days, it's 
just the way it is, please be patient.  Sending multiple "please help, 
still no reply" type messages just adds noise to the list, and give people 
who *do* want to help more to read which means it takes that much longer 
to actually reply.

If you need an answer to a question in a hurry: read the archives and the 
docs, experiment, read the code (if you know java), or hire a consultant 
to help you figure it out.

In this specific case, debugQuery=true would have quickly shown you that 
your qs=5 value wasn't making it's way into the "parsedquery" at all, 
which might have helped you understand what was happening.


-Hoss