[
https://issues.apache.org/jira/browse/LUCENE-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107391#comment-14107391
]
Areek Zillur edited comment on LUCENE-5889 at 8/22/14 7:59 PM:
---------------------------------------------------------------
Interesting: Both AnalyzingInfixSuggester & BlendedInfixSuggester implements
Closeable and on close closes the writer and searchmanager it uses. But looking
into the Solr factories and suggest component, there seems to be no way to
close a suggester (close() is never callled). What might happen is, as all the
failing tests re-uses the same 'solrconfig-phrasesuggest.xml', the
*InfixSuggester never closes the writer or the searchmanager and on subsequent
instantiations throws the LockObtainFailedException (as all tests are re-using
the same directory path for the underlying index)?
was (Author: areek):
Interesting: Both AnalyzingInfixSuggester & BlendedInfixSuggester implements
Closeable and on close closes the writer and searchmanager it uses. But looking
into the Solr factories and suggest component, there seems to be no way to
close a suggester (close() is never callled). What might happen is, as all the
failing tests re-uses the same 'solrconfig-phrasesuggest.xml', the
*InfixSuggester never closes the writer or the searchmanager and on subsequent
builds throws the LockObtainFailedException?
> 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: [email protected]
For additional commands, e-mail: [email protected]
