You are correct.
I would recommend to only use the Synonym TokenFilter at index time
unless you have a very good reason to do it at query time.
On 10/05/2009 11:46 AM, darniz wrote:
yes that's what we decided to expand these terms while indexing.
if we have
bayrische motoren werke => bmw
an
yes that's what we decided to expand these terms while indexing.
if we have
bayrische motoren werke => bmw
and i have a document which has bmw in it, searching for text:bayrische does
not give me results. i have to give
text:"bayrische motoren werke" then it actually takes the synonym and gets
me
On 10/02/2009 06:02 PM, darniz wrote:
Thanks
As i said it even works by giving double quotes too.
like carDescription:"austin martin"
So is that the conclusion that in order to map two word synonym i have to
always enclose in double quotes, so that it doen not split the words
Yes, but
Thanks
As i said it even works by giving double quotes too.
like carDescription:"austin martin"
So is that the conclusion that in order to map two word synonym i have to
always enclose in double quotes, so that it doen not split the words
Christian Zambrano wrote:
>
> When you use a
When you use a field qualifier(fieldName:valueToLookFor) it only applies
to the word right after the semicolon. If you look at the debug
infomation you will notice that for the second word it is using the
default field.
carDescription:austin *text*:martin
the following should word:
carDescri
This is not working when i search documents i have a document which contains
text aston martin
when i search carDescription:"austin martin" i get a match but when i dont
give double quotes
like carDescription:austin martin
there is no match
in the analyser if i give austin martin with out quote
> Hi
> i have a question regarding synonymfilter
> i have a one way mapping defined
> austin martin, astonmartin => aston martin
>
...
>
> Can anybody please explain if my observation is correct. This is a very
> critical aspect for my work.
That is correct - the synonym filter can recognize mul
