You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2016/11/16 18:19:58 UTC

[jira] [Created] (LUCENE-7564) AnalyzingInfixSuggester should close its IndexWriter by default at the end of build()

Steve Rowe created LUCENE-7564:
----------------------------------

             Summary: AnalyzingInfixSuggester should close its IndexWriter by default at the end of build()
                 Key: LUCENE-7564
                 URL: https://issues.apache.org/jira/browse/LUCENE-7564
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Steve Rowe


From SOLR-6246, where AnalyzingInfixSuggester's write lock on its index is causing trouble when reloading a Solr core:

[~gsingers] wrote:
bq. One suggestion that might minimize the impact: close the writer after build

[~varunthacker] wrote:
{quote}
This is what I am thinking -

Create a Lucene issue in which {{AnalyzingInfixSuggester#build}} closes the writer by default at the end.
The {{add}} and {{update}} methods call {{ensureOpen}} and those who do frequent real time updates directly via lucene won't see any slowdowns.

[~mikemccand] - Would this approach have any major drawback from Lucene's perspective? Else I can go ahead an tackle this in a Lucene issue
{quote}

[~mikemccand] wrote:

bq. Fixing {{AnalyzingInfixSuggester}} to close the writer at the end of build seems reasonable?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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