Reading the wiki, one can see that the synonyms are added to the query, when
synonym-expanding at querytime is true. That means instead of searching only
for nice you search for example for nice | pretty.
I suggest you to read the wiki, searching for synonymFilter, and consider
the noticed
Hello,
Brievly, what I'm looking for is a query that launch
something like this:
Giving the user search expression
A B C D
Generated Lucene query :
(myfield:I OR myfield:J OR myfield:O OR myfield:K)
if someone knows a way to reach this goal, please tell me how, i'm
actually
Yonik Seeley wrote:
Are you using the synonyms at index time, query time, or both?
Did you reindex if you made changes to an index analyzer?
It would help if you post the fieldtype for the field you are searching.
I am using the synonyms only at query time.
Below is the field analysis.
: I am using the synonyms only at query time.
: Below is the field analysis.
FYI: I think what yonik ment was the section of your schema.xml that
defines the fieldtype.
: It seems like the culpit is the space in the phrase best buy in
: synonyms.txt.
because of some limitations in the way
On 2/13/07, Chris Hostetter [EMAIL PROTECTED] wrote:
: I am using the synonyms only at query time.
: Below is the field analysis.
FYI: I think what yonik ment was the section of your schema.xml that
defines the fieldtype.
: It seems like the culpit is the space in the phrase best buy in
:
: To be clear, no clean way to do *expansion* as opposed to reduction at
: query time, when the alternatives are of different lengths.
Reduction at query time doesn't work either ... when query parser sees the
string:
my best buy
...it analyzes each white space sepearted string
On 2/13/07, Chris Hostetter [EMAIL PROTECTED] wrote:
: To be clear, no clean way to do *expansion* as opposed to reduction at
: query time, when the alternatives are of different lengths.
Reduction at query time doesn't work either ... when query parser sees the
string:
my best buy
