Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of sanmestry@gmail.com designates
 209.85.160.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <69854147AA9F4DB19BFEA2CDC6B33AC7@JackKrupansky>
References: <1366882380781-4058865.post@n3.nabble.com>
	<591B81AF05D74BBC89DD3F00D09D9CDE@JackKrupansky>
	<1366891236354-4058890.post@n3.nabble.com>
	<24B502B670DA4C0F9D269BDD1FF1BC36@JackKrupansky>
	<1366893827121-4058907.post@n3.nabble.com>
	<CAFz7oVkwv1o=5EUSJfpoiDR2HyMLQgnHXsnyzUDXpYGXdajvkQ@mail.gmail.com>
	<1366901105746-4058929.post@n3.nabble.com>
	<69854147AA9F4DB19BFEA2CDC6B33AC7@JackKrupansky>
Date: Thu, 25 Apr 2013 16:31:07 +0100
Message-ID: 
 <CADS_titxS3QED5ArKADL1AbcAJy3Wx7egQDfPu8rT7BP-6QhKQ@mail.gmail.com>
Subject: Re: Exact matching in Solr 3.6.1
From: Sandeep Mestry <sanmestry@gmail.com>
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=047d7bf17d6c7ab7f604db311b9a

--047d7bf17d6c7ab7f604db311b9a
Content-Type: text/plain; charset=ISO-8859-1

Agree with Jack.

The current field type text_general is designed to match the query tokens
instead of exact matches - so it's not able to fulfill your requirements.

Can you use flat file
<http://wiki.apache.org/solr/FileBasedSpellChecker>as spell check
dictionary instead and that way you can search on exact
matched field while generating spell check suggestions from the file
instead of from index?

-S


On 25 April 2013 16:25, Jack Krupansky <jack@basetechnology.com> wrote:

> Well then just do an exact match ONLY!
>
> It sounds like you haven't worked out the inconsistencies in your
> requirements.
>
> To be clear: We're not offering you "solutions" - that's your job. We're
> only pointing out tools that you can use. It is up to you to utilize the
> tools wisely to implement your solution.
>
> I suspect that you simply haven't experimented enough with various boosts
> to assure that the unstemmed result is consistently higher.
>
> Maybe you need a custom stemmer or stemmer overide so that "passengers"
> does get stemmed to "passenger", but "cats" does not (but "dogs" does.)
> That can be a choice that you can make, but I would urge caution. Still, it
> is a decision that you can make - it's not a matter of Solr forcing or
> preventing you. I still think boosting of an unstemmed field should be
> sufficient.
>
> But until you clarify the inconsistencies in your requirements, we won't
> be able to make much progress.
>
>
> -- Jack Krupansky
>
> -----Original Message----- From: vsl
> Sent: Thursday, April 25, 2013 10:45 AM
>
> To: solr-user@lucene.apache.org
> Subject: Re: Exact matching in Solr 3.6.1
>
> Thanks for your reply but this solution does not fullfil my requirment
> because other documents (not exact matched) will be returned as well.
>
>
>
> --
> View this message in context: http://lucene.472066.n3.**
> nabble.com/Exact-matching-in-**Solr-3-6-1-tp4058865p4058929.**html<http://lucene.472066.n3.nabble.com/Exact-matching-in-Solr-3-6-1-tp4058865p4058929.html>
> Sent from the Solr - User mailing list archive at Nabble.com.
>

--047d7bf17d6c7ab7f604db311b9a--