: > You say it's bogus because the qp will divide on whitesapce first -- but : > you're assuming you know what query parser will be used ... the "field" : > query parser (to name one) doesn't split on whitespace first. That's my : > point: analysis.jsp doesn't make any assumptions about what query parser : > *might* be used, it just tells you what your analyzers do with strings. : > : : you're right, we should just fix the bug that the queryparser tokenizes on : whitespace first. then analysis.jsp will be significantly less confusing.
dude .. not trying to get into a holy war here even if you change the Lucene QUeryParser so that whitespace isn't a meta character it doens't affect the underlying issue: analysis.jsp is agnostic about QueryParsers. Some other QParser the users uses might have other special behavior and if people don't understand hte distinction between QueryParsing and analysis they can still be confused -- hell even if the only QParser anyone ever uses is the lucene QParser, and even if you get the QUeryParser changed so that whitespace isn't a metacharacter, you we are still going to be left with the fact that *other* charaters (like '+' and '-' and '"' and '*' and ...) are metacharacters for that query parser, and have special meaning. analysis.jsp isn't going to know about those, or do anything special for them -- so people cna still be easily confused when analysis.jsp says one thing about how the string "+foo* -bar" get's analyzed, but that string as a query means something completley different. Hence my point: leave arguments about QueryParser out of it -- how do we make the function of analysis.jsp more clear? -Hoss
