On Dec 27, 2005, at 1:45 PM, Dmitry Goldenberg wrote:
I tried using Porter stemming in our application and it worked
great except it broke the proximity searches. Is there any way at
all that these two pieces of functionality could coexist peacefully?
I do not see any reason why they should not. It seems to me that
proximity query terms should be stemmed by the engine, then the
query executed. Personally, I would not care much if the following
two proximity queries would bring back the same results:
"character encoding"~3
and
"characters encode"~3
I'd much rather they both returned the same results than no results
at all, the latter being the case I've observed.
Any recommendations?
Are you using the same Analyzer with QueryParser as you are with
IndexWriter? What does the generated Query.toString yield?
This absolutely works provided the analyzers jive between indexing
and searching.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
