Thanks for the Feedback.
I have few questions for clarifications...
>
> Some mistakes here:
>
> >The syntax above is for strings the query parser expect to find AFTER
> passing the query string through the analyzer in use. If your
> analyzer may drop (e.g. StopFilter) or add tokens, this may result in
> trying to parse an invalid string.
>
> Not correct. The query parser passes the term text through the
> analyzer, and knows how to deal with the case where the analyzer drops
> terms or expands terms.
Does the parser passes each term through a fresh analyzer and
handle any number of terms returned from the analyzer for that term ?
I remember that having somthing like '+strong +will' created an exception
because
'will' was droped by the ProterStemer. Did you fix that ? What about the
case were
'strong' is replaced by the anlyzer with 'strong' and 'tough' ? Will the
parser convert
it to '+( strong OR tough) +will' ?
>
> With respect to the new support for prefix query, you should note that:
> - if a prefix is included, then the associated string won't get processed
> by the analyzer
Will the prefix query handle case differences ? That is, if the document
was indexed with the lowercase filter and the prefix 'DO*' is used, will it
match 'dogs' ?
Also, what if the document were indexed with
PorterStemer, will 'dogs*' match 'dogs' ?
> - You can't put a prefix term inside a phrase ("foo* bar")
I think this is clear from the syntax.
Tal
>
> _______________________________________________
> Lucene-dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/lucene-dev
>
_______________________________________________
Lucene-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/lucene-dev
