t_en_splitting and delete the
PorterStemFilterFactory filter from both the query and index analyzers.
-- Jack Krupansky
-Original Message- From: Rohan Thakur
Sent: Wednesday, March 20, 2013 8:39 AM
To: solr-user@lucene.apache.org
Subject: Re: had query regarding the indexing and analys
f text_en_splitting and delete the
> PorterStemFilterFactory filter from both the query and index analyzers.
>
>
> -- Jack Krupansky
>
> -Original Message- From: Rohan Thakur
> Sent: Wednesday, March 20, 2013 8:39 AM
>
> To: solr-user@lucene.apache.org
> Subject: Re:
dnesday, March 20, 2013 8:39 AM
To: solr-user@lucene.apache.org
Subject: Re: had query regarding the indexing and analysers
hi jack
I have been using text_en_splitting initially but what it was doing is it
is changing by query aswell
for example:
if i am searching for "ace" term it is
al to a
> compound term (e.g., "CD-ROM") or a phrase separator as in your case. Some
> people are careful to put spaces around the hyphen for a phrase delimiter,
> but plenty of people still just drop it in directly adjacent to two words.
>
> In your case, text_en_splitting_tight is SP
ue here is that the former does not have generateWordParts="1".
That is the option that is needed so that "Laptop-DUAL" will be indexed as
"laptop dual".
-- Jack Krupansky
-Original Message-
From: Rohan Thakur
Sent: Tuesday, March 19, 2013 3:35 AM
To: solr-us
Please review: http://wiki.apache.org/solr/UsingMailingLists. You're
forcing us to guess at what's going on. You haven't posted the
results of adding debug=query (or debug=all). You haven't shown
us the field definitions for the fields in question. You haven't
given us much info to help us help yo
my default is title only I have used debug as well it shows that solr
divides the query into dual and core and then searches both separately now
while calculating the scores it puts the document in which both the terms
appear and in my case the document containing this title:
Wipro 7710U Laptop-D
See admin/analysis, it's invaluable. Probably
The terms are being searched against your default text field which I'd
guess is not "title".
Also, try adding &debug=all to your query and look in the debug info at the
parsed form of the query to see what's actually being searched.
Best
Erick
On F
