Without the parens, the "edgytext:" only applied to "Mr", the default
field still applied to "Scorcese".
The double quotes are neccesary in the second case (rather than parens),
because on a non-tokenized field because the standard query parser will
"pre-tokenize" on whitespace before sending individual white-space
seperated words to match the index. If the index includes multi-word
tokens with internal whitespace, they will never match. But the standard
query parser doesn't "pre-tokenize" like this, it passes the whole
phrase to the index intact.
Robert Gründler wrote:
Did you run your query without using () and "" operators? If yes can you try
this?
&q=edgytext:(Mr Scorsese) OR edgytext2:"Mr Scorsese"^2.0
I didn't use () and "" in my query before. Using the query with those operators
works now, stopwords are thrown out as the should, thanks.
However, i don't understand how the () and "" operators affect the
StopWordFilter.
Could you give a brief explanation for the above example?
thanks!
-robert
