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

Hoss Man commented on LUCENE-5889:
----------------------------------

bq. Is there a thread safety issue with the writer in AnalyzingInfixSuggester 
here?

there's definitely a lock not getting freed somewhere - but i don't know about 
thread safety.

bq. I am currently investigating the problem, will update when I find anything 
interesting.

Thanks areek.

NOTE: it's totally possible that this change itself is fine and correct, and 
just happened to tickle some existing bug in the Solr factories that wrap the 
suggesters


> AnalyzingInfixSuggester should expose commit()
> ----------------------------------------------
>
>                 Key: LUCENE-5889
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5889
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/spellchecker
>            Reporter: Mike Sokolov
>             Fix For: 5.0, 4.11
>
>         Attachments: LUCENE-5889.patch, LUCENE-5889.patch
>
>
> There is no way short of close() for a user of AnalyzingInfixSuggester to 
> cause it to commit() its underlying index: only refresh() is provided.  But 
> callers might want to ensure the index is flushed to disk without closing.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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

Reply via email to