You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2006/10/25 05:53:16 UTC
[jira] Created: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Scorer.skipTo affects sloppyPhrase scoring
------------------------------------------
Key: LUCENE-697
URL: http://issues.apache.org/jira/browse/LUCENE-697
Project: Lucene - Java
Issue Type: Bug
Components: Search
Affects Versions: 2.0.0
Reporter: Yonik Seeley
If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Updated: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-697?page=all ]
Doron Cohen updated LUCENE-697:
-------------------------------
Lucene Fields: [Patch Available] (was: [New])
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: http://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
> Assigned To: Doron Cohen
> Attachments: sloppy_phrase_skipTo.patch
>
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Commented: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-697?page=comments#action_12444756 ]
Yonik Seeley commented on LUCENE-697:
-------------------------------------
> Yonik, this is uassigned, are you working on a fix for this?
Nope, feel free to grab it :-)
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: http://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Commented: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-697?page=comments#action_12444565 ]
Yonik Seeley commented on LUCENE-697:
-------------------------------------
Here's the ant output from test code to be checked in shortly.
The test code calls skipTo(), skipTo(), next(), next(), etc
while checking that the results match the hitcollector version.
[junit] Testcase: testP6(org.apache.lucene.search.TestSimpleExplanations):
Caused an ERROR
[junit] ERROR matching docs:
[junit] scorer.more=true doc=1 score=0.7849069
[junit] hitCollector.doc=1 score=0.67974937
[junit] Scorer=scorer(weight(field:"w3 w2"~2))
[junit] Query=field:"w3 w2"~2
[junit] Searcher=org.apache.lucene.search.IndexSearcher@118f375
[junit] java.lang.RuntimeException: ERROR matching docs:
[junit] scorer.more=true doc=1 score=0.7849069
[junit] hitCollector.doc=1 score=0.67974937
[junit] Scorer=scorer(weight(field:"w3 w2"~2))
[junit] Query=field:"w3 w2"~2
[junit] Searcher=org.apache.lucene.search.IndexSearcher@118f375
[junit] at org.apache.lucene.search.QueryUtils$2.collect(QueryUtils.java
:104)
[junit] at org.apache.lucene.search.Scorer.score(Scorer.java:48)
[junit] at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.j
ava:132)
[junit] at org.apache.lucene.search.Searcher.search(Searcher.java:116)
[junit] at org.apache.lucene.search.Searcher.search(Searcher.java:95)
[junit] at org.apache.lucene.search.QueryUtils.checkSkipTo(QueryUtils.ja
va:97)
[junit] at org.apache.lucene.search.QueryUtils.check(QueryUtils.java:75)
[junit] at org.apache.lucene.search.CheckHits.checkHitCollector(CheckHit
s.java:91)
[junit] at org.apache.lucene.search.TestExplanations.qtest(TestExplanati
ons.java:90)
[junit] at org.apache.lucene.search.TestExplanations.qtest(TestExplanati
ons.java:86)
[junit] at org.apache.lucene.search.TestSimpleExplanations.testP6(TestSi
mpleExplanations.java:87)
[junit] Testcase: testP7(org.apache.lucene.search.TestSimpleExplanations):
Caused an ERROR
[junit] ERROR matching docs:
[junit] scorer.more=true doc=1 score=0.7849069
[junit] hitCollector.doc=1 score=0.67974937
[junit] Scorer=scorer(weight(field:"w3 w2"~3))
[junit] Query=field:"w3 w2"~3
[junit] Searcher=org.apache.lucene.search.IndexSearcher@1dd7056
[junit] java.lang.RuntimeException: ERROR matching docs:
[junit] scorer.more=true doc=1 score=0.7849069
[junit] hitCollector.doc=1 score=0.67974937
[junit] Scorer=scorer(weight(field:"w3 w2"~3))
[junit] Query=field:"w3 w2"~3
[junit] Searcher=org.apache.lucene.search.IndexSearcher@1dd7056
[junit] at org.apache.lucene.search.QueryUtils$2.collect(QueryUtils.java
:104)
[junit] at org.apache.lucene.search.Scorer.score(Scorer.java:48)
[junit] at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.j
ava:132)
[junit] at org.apache.lucene.search.Searcher.search(Searcher.java:116)
[junit] at org.apache.lucene.search.Searcher.search(Searcher.java:95)
[junit] at org.apache.lucene.search.QueryUtils.checkSkipTo(QueryUtils.ja
va:97)
[junit] at org.apache.lucene.search.QueryUtils.check(QueryUtils.java:75)
[junit] at org.apache.lucene.search.CheckHits.checkHitCollector(CheckHit
s.java:91)
[junit] at org.apache.lucene.search.TestExplanations.qtest(TestExplanati
ons.java:90)
[junit] at org.apache.lucene.search.TestExplanations.qtest(TestExplanati
ons.java:86)
[junit] at org.apache.lucene.search.TestSimpleExplanations.testP7(TestSi
mpleExplanations.java:90)
[junit] Test org.apache.lucene.search.TestSimpleExplanations FAILED
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: http://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Commented: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-697?page=comments#action_12454844 ]
Doron Cohen commented on LUCENE-697:
------------------------------------
I went on documenting sloppy phrase scorer and phrase scorer, so that the fix above can make it in more comfortably.
However while doing that I found that the scorer does not behave as I thought it should.
It seems to me that a problem with sloppy phrase scoring is broader then the skipTo() behavior, and actually the skipTo behavior is just a side effect of that.
So I am creating a new issue to discuss sloppy phrase scoring behavior, that if/when resolved would probably also reolve this one.
See https://issues.apache.org/jira/browse/LUCENE-736
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: http://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
> Assigned To: Doron Cohen
> Attachments: sloppy_phrase_skipTo.patch, sloppy_phrase_skipTo.patch2
>
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Commented: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-697?page=comments#action_12447205 ]
Yonik Seeley commented on LUCENE-697:
-------------------------------------
Thanks for tackling this one Doron!
Wow is that phrase code complex! I think I may need to step through an example or two before I really get it.
Anyway, the changes you suggest all look logical in context... It's just some of the rest of the phrase scoring code I'm still trying to understand.
Regarding the sort:
+ if (pp1.position == pp2.position)
+ return pp1.position+pp1.offset < pp2.position+pp2.offset;
Surely this degenerates to
if (pp1.position == pp2.position)
return pp1.offset < pp2.offset;
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: http://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
> Assigned To: Doron Cohen
> Attachments: sloppy_phrase_skipTo.patch, sloppy_phrase_skipTo.patch2
>
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Updated: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Anonymous (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-697?page=all ]
Attachment: sloppy_phrase_skipTo.patch2
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: http://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
> Assigned To: Doron Cohen
> Attachments: sloppy_phrase_skipTo.patch, sloppy_phrase_skipTo.patch2
>
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Commented: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-697?page=comments#action_12445795 ]
Doron Cohen commented on LUCENE-697:
------------------------------------
An updated version of this patch - sloppy_phrase_skipTo.patch2.
I modified QueryUtils.java (test util) to test all the sequences, not just one.
It is also now quite easy to add a new sequence to be tested, if needed.
Other changes in this patch remain:
- PhraseQueue: this is the fix.
- ExactPhraseScorer: added call to clear queue - not a must, but cleaner this way.
- PhraseScorer: added mark that init done at skip - again not a must, just cleaner this way.
All "ant test" tests pass.
- Doron
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: http://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
> Assigned To: Doron Cohen
> Attachments: sloppy_phrase_skipTo.patch, sloppy_phrase_skipTo.patch2
>
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Updated: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-697?page=all ]
Doron Cohen updated LUCENE-697:
-------------------------------
Attachment: sloppy_phrase_skipTo.patch
This was tricky, for me anyhow, but I think I found it.
The difference in scoring between using next() to using skipTo() (or a combination of these two) is caused by two (valid) orders of the sorted PhrasePositions.
Currently PhrasePositions sorting is defined by doc and position, where position already considers the offset of the term within the (phrase) query.
If however two TermPosition have the same doc and same position, the sort takes no decision, which falls down to one valid sort (by current sort definition). The difference between using next() and skipTo() in this regard is that skipTo() always calls sort(), sorting the entire set, while next() only calls sort() at initialization and then maintain the sorting as part of the scoring process.
This would be clearer with the following example - taken from Yonik's test case that is failing now:
- Doc1: w1 w3 w2 w3 zz
- Query: "w3 w2"~2
When starting scoring in this doc, both PhrasePositions pp(w3) and pp(w2) have doc(2)=doc(w3)=1.
Note, that, for the second w3 that matches we would have pos(w2)=2+1=3 and pos(w3)=3+0=3.
So, after scoring doc1("w3 w2"), if the sort result places pp(w2) at the top, we would also score for doc1("w3 w2"). However, if pp(w3) is placed by the sort at the top (==smallest), we would not score also for doc1("w3 w2").
Current behavior is inconsistent: skip() would take the two while next() won't, and I think it is possible to create a case where it would be the other way around. So definitely behavior should be made consistent.
Next question to be asked is: Do we want to sum (or max) the frequency for both (or more cases)? I think yes, sum.
To fix this I am changing PhrasePosition comparison, so that in case positions are equal, the actual doc position (ignoring offset in query phrase) is considered.
In addition, I added missing calls to clear the priority queue before starting to sort and to mark that no more initialization is required when skipTo() is called.
I tested with the sequence that Yonik added:
- skip skip next next skip skip
And also with the sequences:
- skip skip skip skip skip skip
- next next next next next next
- skip next skip next skip next
- next skip next skip next skip
- next next skip skip next next
The latter 5 cases are now commented out, the first case is in effect.
This scoring code is still not feeling natural to me, so (actually as always) comments will be appreciated.
- Doron
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: http://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
> Assigned To: Doron Cohen
> Attachments: sloppy_phrase_skipTo.patch
>
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Assigned: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-697?page=all ]
Doron Cohen reassigned LUCENE-697:
----------------------------------
Assignee: Doron Cohen
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: http://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
> Assigned To: Doron Cohen
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Commented: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-697?page=comments#action_12444744 ]
Doron Cohen commented on LUCENE-697:
------------------------------------
I can reproduce this by uncommenting this line.
Interesting to notice that:
(1) the sequence to next() next() skip() skip() next() next() (!= instead of ==) passes the tests.
This is exoected because the problem is in the initialization (at least in PhraseQuery).
(2) the sequence next() skip() next() does not work (..&0x01)!=0 instead of &0x02)==0) does not pass.
This is surprising to me - becuase seemingly there are no initialization issues here.
But I think the cause is that, at least in PhraseQuery, it is not just an intialization issue.
Yonik, this is uassigned, are you working on a fix for this?
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: http://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Commented: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-697?page=comments#action_12447234 ]
Doron Cohen commented on LUCENE-697:
------------------------------------
You're right Yonik, pp1.offset < pp2.offset is equivalent.
However note that pp1.position + pp1.offset == tp1.position, i.e. by adding the (query) offset we compare the termPosition offsets, as read from the index.
Just to complete the setting - having pp.position == tp.position - offset allows the phrase scorer to identify a match when all pp.positions are the same (for exact) or distant no more than slope (for sloppy).
So we should probably return the simpler expression as you suggest, and comment the code, something like this:
if (pp1.doc == pp2.doc)
if (pp1.position == pp2.position)
// Same doc and pp.positions, so compare *actual term positions*.
// Since pp.position == tp.position - (query) offset,
// can restore tp.position as pp.position + offset.
// But pp.positions are equal, so can just compare the offsets.
return pp1.offset < pp2.offset;
else
return pp1.position < pp2.position;
else
return pp1.doc < pp2.doc;
makes sense?
Perhaps it would be nice if we also add some code comments to the scorers...?
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: http://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
> Assigned To: Doron Cohen
> Attachments: sloppy_phrase_skipTo.patch, sloppy_phrase_skipTo.patch2
>
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Commented: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LUCENE-697?page=comments#action_12444573 ]
Yonik Seeley commented on LUCENE-697:
-------------------------------------
Comment out line 104 of QueryUtils.java to reproduce this problem:
scoreDiff=0; // TODO: remove this go get LUCENE-697 failures
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: http://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org
[jira] Resolved: (LUCENE-697) Scorer.skipTo affects sloppyPhrase
scoring
Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doron Cohen resolved LUCENE-697.
--------------------------------
Resolution: Duplicate
Fixed by LUCENE-736 .
> Scorer.skipTo affects sloppyPhrase scoring
> ------------------------------------------
>
> Key: LUCENE-697
> URL: https://issues.apache.org/jira/browse/LUCENE-697
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.0.0
> Reporter: Yonik Seeley
> Assigned To: Doron Cohen
> Attachments: sloppy_phrase_skipTo.patch, sloppy_phrase_skipTo.patch2
>
>
> If you mix skipTo() and next(), you get different scores than what is returned to a hit collector.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org