[ http://issues.apache.org/jira/browse/LUCENE-736?page=all ]
Doron Cohen updated LUCENE-736:
---
Attachment: sloppy_phrase.patch2.txt
res-search-orig2.log
res-search-new2.log
The change to fix case 2 was not the main
[ http://issues.apache.org/jira/browse/LUCENE-736?page=all ]
Doron Cohen updated LUCENE-736:
---
Lucene Fields: [New, Patch Available] (was: [New])
Sloppy Phrase Scoring Misbehavior
-
Key: LUCENE-736
[
http://issues.apache.org/jira/browse/LUCENE-736?page=comments#action_12455085 ]
Paul Elschot commented on LUCENE-736:
-
There is no need to hold up this issue for span phrases.
Perhaps a good way to get the spans and the phrases work well
[
http://issues.apache.org/jira/browse/LUCENE-707?page=comments#action_12455090 ]
Grant Ingersoll commented on LUCENE-707:
Thanks, I was wondering how to do that!
--
Grant Ingersoll
Center for Natural Language
At the contrary Mike, I am beginning to think that there have been a number
of misunderstandings, of my original posting to start with.
When I submitted my proposal I was prepared for some discussion on the
merits or otherwise of my proposed solution. I had no idea that the
discussion would
I think the point of the discussion is really to determine the answer
to #1.
I would counter that it is not a compelling feature for MOST users of
Lucene, but it can still be implemented externally using binary
fields for those that require it, and or even easier (and maybe even
faster)
