[ 
https://issues.apache.org/jira/browse/LUCENE-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585935#comment-13585935
 ] 

William Johnson commented on LUCENE-4783:
-----------------------------------------

This is odd, as of this morning, I can't make it happen any more.

This problem has been on-again off-again, and currently it's off.  If it starts 
happening again, I'll see if I can find more specifics as to what in particular 
is happening at the time it happens, but for now I suppose I should close the 
issue as something I can't repeat.
                
> Inconsistent results, changing based on recent previous searches (caching?)
> ---------------------------------------------------------------------------
>
>                 Key: LUCENE-4783
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4783
>             Project: Lucene - Core
>          Issue Type: Bug
>    Affects Versions: 4.1
>         Environment: Ubuntu Linux & Java application running under Tomcat
>            Reporter: William Johnson
>
> We have several repeatable cases where Lucene is returning different 
> candidates for the same search, on the same (static) index, depending on what 
> other searches have been run before hand.
> It appears as though Lucene is failing to find matches in some cases if they 
> have not been cached by a previous search.
> In specific (although it is happening with more than just fuzzy searches), a 
> fuzzy search on a misspelled street name returns no result.  If you then 
> search on the correctly spelled street name, and THEN return to the original 
> fuzzy query on the original incorrect spelling, you now receive the result.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to