Yonik Seeley wrote:
From the user's point of view I think it will make sense to
build a phrase query only when the quotes are found in the search string.
You make an interesting point Sergiu. Your proposal would increase
the expressive power of the QueryParser by allowing the constructio
> From the user's point of view I think it will make sense to
> build a phrase query only when the quotes are found in the search string.
You make an interesting point Sergiu. Your proposal would increase
the expressive power of the QueryParser by allowing the construction
of either phrase querie
Chris Hostetter wrote:
: Exactly this is my question, why the QueryParser creates a Phrase query
: when he gets several tokens from analyzer
: and not a BooleanQuery?
Because if it did that, there would be no way to write phrase queries :)
I'm not very sure about this ...
QueryParser only
: >they key to understanding why that resulted in a phrase query instead of
: >three term queries is that QueryParser doesn't treat comma as a special
: >character, so it saw the string word1,word2,word3 and gave it to your
: >analyzer. Since your analyzer gave back several tokens QueryParser bui
Chris Hostetter wrote:
: I built a wrong query string "word1,word2,word3" instead of "word1
: word2 word3"
: therefore I got a wrong query: field:"word1 word2 word3" instead of
: field:word1 field:word2 field:word3.
:
: Is this an espected behaviour?
: I used Standard analyzer, probably the
: I built a wrong query string "word1,word2,word3" instead of "word1
: word2 word3"
: therefore I got a wrong query: field:"word1 word2 word3" instead of
: field:word1 field:word2 field:word3.
:
: Is this an espected behaviour?
: I used Standard analyzer, probably therefore, the comas were re
