[
https://issues.apache.org/jira/browse/LUCENE-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107228#comment-14107228
]
Mark Miller commented on LUCENE-5889:
-------------------------------------
bq. but i don't know about thread safety.
It's hard to know at a glance, but the class is written in a way that says it
expects to be used by multiple threads and the indexwriter is not accessed in a
way that expects to be used by multiple threads. No fire, but a bunch of smoke.
> 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
