I agree with that assessment. I hadn't taken the time to look at the patch, but I am in agreement that the fix should be "stop QueryParser from interpreting characters as operators when there is no whitespace surrounding them". As long as the QP doesn't do anything in this case, the Analyzer will be able to handle it the same way it did when indexing (which is what we want).
-Mike
At 12:57 PM 10/20/2003, you wrote:
On Wednesday, October 15, 2003, at 10:24 AM, Michael Giles wrote:
I looked at the patch here:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23838
I'm not entirely satisfied with it. I'm of the opinion that we should only change QueryParser to fix the behavior of operators nestled within text with no surrounding whitespace. The provided patch only works with the "-" character, but what about "Wal+Mart"? Shouldn't we keep that together also and hand it to the analyzer?
I'm not convinced at all that we should change the StandardTokenizer to not split on dash. If only QueryParser was fixed and handed "Wal-Mart" to the StandardAnalyzer, it would be split the same way as during indexing and searches would return the expected hits.
Thoughts? I'd like to see this fixed, but in a way that makes the most general sense.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
