You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2011/06/20 05:46:47 UTC

[jira] [Created] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

SloppyPhraseScorer sometimes computes Infinite freq
---------------------------------------------------

                 Key: LUCENE-3215
                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
             Project: Lucene - Java
          Issue Type: Bug
            Reporter: Robert Muir
         Attachments: LUCENE-3215_test.patch

reported on user list:
http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Updated] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir updated LUCENE-3215:
--------------------------------

    Attachment: LUCENE-3215_test.patch

those lyrics are entertaining, but here is a more concise test.

> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>         Attachments: LUCENE-3215_test.patch, LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Commented] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107209#comment-13107209 ] 

Doron Cohen commented on LUCENE-3215:
-------------------------------------

OK I think I have a fix for this.

While looking at it, I realized that PhraseScorer (the one that used to base both Exact&Sloppy phrase scorers but now is the base of only sloppy phrase scorer) is way too complicated and inefficient. All those sort calls after each matching doc can be avoided. 

So I am modifying PhraseScorer to not have a phrase-queue at all - just the sorted linked list, which is always kept sorted by advancing last beyond first. Last is renamed to 'min' and first is renamed to 'max'. Making the list cyclic allows more efficient manipulation of it. 

With this, SloppyPhraseScorer is modified to maintain its own phrase queue. The queue size is set at the first candidate document. In order to handle repetitions (Same term in different query offsets) it will contain only some of the pps: those that either have no repetitions, or are the first (lower query offset) in a repeating group. A linked list of repeating pps was added: so PhrasePositions has a new member: nextRepeating.

Detection of repeating pps and creation of that list is done once per scorer: at the first candidate doc.

For solving the bugs reported here, in addition to the initiation of 'end' as explained in previous comment, advanceRepeatingPPs now also update two values:
- end, in case one of the repeating pps is far ahead (larger)
- position of the first pp in a repeating list (the one that is in the queue - in case the repeating pp is far behind (smaller). This can happen when there are holes in the query, as position = tpPOs - offset. It fixes the problem of false negative distances which caused this bug. It is tricky: relies on that PhrasePositions.nextPosition() ignores pp.position and just call positions.nextPosition(). But it is correct, as the modified position is used to replace pp in the queue.

Last, I think that the test added with holes had one wrong assert: It added four docs:
- drug drug
- drug druggy drug
- drug druggy druggy drug
- drug druggy drug druggy drug
defined this query (number is the offset):
- drug(1) drug(3)
and expected that with slop=1 the first doc would not be found.
I think it should be found, as the slop operates in both directions.
So modified the query to: drug(1) drug(3)

Patch to follow.

> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Doron Cohen
>         Attachments: LUCENE-3215.patch, LUCENE-3215_test.patch, LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Commented] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100182#comment-13100182 ] 

Doron Cohen commented on LUCENE-3215:
-------------------------------------

An update on this...

This is not related to LUCENE-3142 - the latter was fixed but this one still fails.

The patch fix which 'abs' the distance indeed avoids the infinite score problem, but I was not 100% comfortable with it - how can the distance be none positive?

Digging into it shows a wrong assumption in SloppyPhraseScorer:

{code}
    private int initPhrasePositions() throws IOException {
        int end = 0;
{code}

The initial value of end assumes that all positions will be nonnegative.
But this is wrong, as PP position is computed as 

{code}
  position = postings.nextPosition() - offset
{code}

So, whenever the query term appears in the doc in a position smaller than its offset in the query, the computed position is negative. The correct initialization for end is therefore:

{code}
    private int initPhrasePositions() throws IOException {
        int end = Integer.MIN_VALUE;
{code}

You would expect this bug to surfaced sooner...

Anyhow, for the 3 tests that Robert added, this only resolve testInfiniteFreq1() but the other two tests still fail, investigating...

> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Doron Cohen
>         Attachments: LUCENE-3215.patch, LUCENE-3215_test.patch, LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Updated] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir updated LUCENE-3215:
--------------------------------

    Attachment: LUCENE-3215.patch

Here's a hack patch... 

I tried writing some correctness tests here but its *really* hard for me to visualize what the freq should even be for these "sloppy repeating phrase queries with holes".


> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>         Attachments: LUCENE-3215.patch, LUCENE-3215_test.patch, LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Issue Comment Edited] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107209#comment-13107209 ] 

Doron Cohen edited comment on LUCENE-3215 at 9/17/11 6:56 PM:
--------------------------------------------------------------

OK I think I have a fix for this.

While looking at it, I realized that PhraseScorer (the one that used to base both Exact&Sloppy phrase scorers but now is the base of only sloppy phrase scorer) is way too complicated and inefficient. All those sort calls after each matching doc can be avoided. 

So I am modifying PhraseScorer to not have a phrase-queue at all - just the sorted linked list, which is always kept sorted by advancing last beyond first. Last is renamed to 'min' and first is renamed to 'max'. Making the list cyclic allows more efficient manipulation of it. 

With this, SloppyPhraseScorer is modified to maintain its own phrase queue. The queue size is set at the first candidate document. In order to handle repetitions (Same term in different query offsets) it will contain only some of the pps: those that either have no repetitions, or are the first (lower query offset) in a repeating group. A linked list of repeating pps was added: so PhrasePositions has a new member: nextRepeating.

Detection of repeating pps and creation of that list is done once per scorer: at the first candidate doc.

For solving the bugs reported here, in addition to the initiation of 'end' as explained in previous comment, advanceRepeatingPPs now also update two values:
- end, in case one of the repeating pps is far ahead (larger)
- position of the first pp in a repeating list (the one that is in the queue - in case the repeating pp is far behind (smaller). This can happen when there are holes in the query, as position = tpPOs - offset. It fixes the problem of false negative distances which caused this bug. It is tricky: relies on that PhrasePositions.nextPosition() ignores pp.position and just call positions.nextPosition(). But it is correct, as the modified position is used to replace pp in the queue.

Last, I think that the test added with holes had one wrong assert: It added four docs:
- drug drug
- drug druggy drug
- drug druggy druggy drug
- drug druggy drug druggy drug

defined this query (number is the offset):
- drug(1) drug(3)

and expected that with slop=1 the first doc would not be found.
I think it should be found, as the slop operates in both directions.
So modified the query to: drug(1) drug(3)

Patch to follow.

      was (Author: doronc):
    OK I think I have a fix for this.

While looking at it, I realized that PhraseScorer (the one that used to base both Exact&Sloppy phrase scorers but now is the base of only sloppy phrase scorer) is way too complicated and inefficient. All those sort calls after each matching doc can be avoided. 

So I am modifying PhraseScorer to not have a phrase-queue at all - just the sorted linked list, which is always kept sorted by advancing last beyond first. Last is renamed to 'min' and first is renamed to 'max'. Making the list cyclic allows more efficient manipulation of it. 

With this, SloppyPhraseScorer is modified to maintain its own phrase queue. The queue size is set at the first candidate document. In order to handle repetitions (Same term in different query offsets) it will contain only some of the pps: those that either have no repetitions, or are the first (lower query offset) in a repeating group. A linked list of repeating pps was added: so PhrasePositions has a new member: nextRepeating.

Detection of repeating pps and creation of that list is done once per scorer: at the first candidate doc.

For solving the bugs reported here, in addition to the initiation of 'end' as explained in previous comment, advanceRepeatingPPs now also update two values:
- end, in case one of the repeating pps is far ahead (larger)
- position of the first pp in a repeating list (the one that is in the queue - in case the repeating pp is far behind (smaller). This can happen when there are holes in the query, as position = tpPOs - offset. It fixes the problem of false negative distances which caused this bug. It is tricky: relies on that PhrasePositions.nextPosition() ignores pp.position and just call positions.nextPosition(). But it is correct, as the modified position is used to replace pp in the queue.

Last, I think that the test added with holes had one wrong assert: It added four docs:
- drug drug
- drug druggy drug
- drug druggy druggy drug
- drug druggy drug druggy drug
defined this query (number is the offset):
- drug(1) drug(3)
and expected that with slop=1 the first doc would not be found.
I think it should be found, as the slop operates in both directions.
So modified the query to: drug(1) drug(3)

Patch to follow.
  
> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Doron Cohen
>         Attachments: LUCENE-3215.patch, LUCENE-3215_test.patch, LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Updated] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doron Cohen updated LUCENE-3215:
--------------------------------

    Attachment: LUCENE-3215.patch

Updated patch for current trunk r1172055.

> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Doron Cohen
>         Attachments: LUCENE-3215.patch, LUCENE-3215.patch, LUCENE-3215.patch, LUCENE-3215_test.patch, LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Commented] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079964#comment-13079964 ] 

Robert Muir commented on LUCENE-3215:
-------------------------------------

It seems to me the root cause of the bug is having position 'holes' (e.g. stopwords), especially across duplicated terms...

For example, if you disable position increments in queryparser it won't trigger the bug.

> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>         Attachments: LUCENE-3215_test.patch, LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Commented] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051786#comment-13051786 ] 

Robert Muir commented on LUCENE-3215:
-------------------------------------

the problem in this case, is it computes a 'matchLength' of -1.
then the default impl of sloppyFreq divides by zero, because its defined as:
{noformat}
return 1.0f / (distance + 1);
{noformat}


> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>         Attachments: LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Updated] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doron Cohen updated LUCENE-3215:
--------------------------------

    Attachment: LUCENE-3215.patch

Previous patch still produces NANs and infinite scores with holes.
Updated patch is fixing this, by updating END (before computing the new match-length) also for pp (not only for its repeats).

I plan to commit this soon.

> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Doron Cohen
>         Attachments: LUCENE-3215.patch, LUCENE-3215.patch, LUCENE-3215.patch, LUCENE-3215.patch, LUCENE-3215_test.patch, LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Updated] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doron Cohen updated LUCENE-3215:
--------------------------------

    Attachment: LUCENE-3215.patch

Attached patch is based on r1166541 - before recent changes to scorers. Will merge with recent changes tomorrow or so. All tests pass.
I believe that sloppy scoring performance should improve with this change but did not check this.

> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Doron Cohen
>         Attachments: LUCENE-3215.patch, LUCENE-3215.patch, LUCENE-3215_test.patch, LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Resolved] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doron Cohen resolved LUCENE-3215.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0
                   3.5

Fixed
- r1173961 - trunk
- r1174002 - 3x

Prior to committing I compared the performance of sloppy phrase queries with/out repeats for large documents with many candidate matches and did not see the anticipated speedup, though, at least, no degradations as well.

> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Doron Cohen
>             Fix For: 3.5, 4.0
>
>         Attachments: LUCENE-3215.patch, LUCENE-3215.patch, LUCENE-3215.patch, LUCENE-3215.patch, LUCENE-3215_test.patch, LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Updated] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir updated LUCENE-3215:
--------------------------------

    Attachment: LUCENE-3215_test.patch

test case

> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>         Attachments: LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Assigned] (LUCENE-3215) SloppyPhraseScorer sometimes computes Infinite freq

Posted by "Doron Cohen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doron Cohen reassigned LUCENE-3215:
-----------------------------------

    Assignee: Doron Cohen

> SloppyPhraseScorer sometimes computes Infinite freq
> ---------------------------------------------------
>
>                 Key: LUCENE-3215
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3215
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Doron Cohen
>         Attachments: LUCENE-3215.patch, LUCENE-3215_test.patch, LUCENE-3215_test.patch
>
>
> reported on user list:
> http://www.lucidimagination.com/search/document/400cbc528ed63db9/score_of_infinity_on_dismax_query

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org