[
https://issues.apache.org/jira/browse/LUCENE-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated LUCENE-1152:
-------------------------------------
Component/s: (was: contrib/*)
contrib/spellchecker
Assignee: Otis Gospodnetic
This patch no longer applies. Could you provide a new patch (against trunk)?
Also, please use 2-spaces for indentation. Thanks.
As for synchronizing indexDictionary method, why not add synchronization logic
to your application?
> SpellChecker does not work properly on calling indexDictionary after
> clearIndex
> -------------------------------------------------------------------------------
>
> Key: LUCENE-1152
> URL: https://issues.apache.org/jira/browse/LUCENE-1152
> Project: Lucene - Java
> Issue Type: Bug
> Components: contrib/spellchecker
> Affects Versions: 2.3
> Reporter: Naveen Belkale
> Assignee: Otis Gospodnetic
> Priority: Minor
> Attachments: spellchecker.diff
>
>
> We have to call clearIndex and indexDictionary to rebuild dictionary from
> fresh. The call to SpellChecker clearIndex() function does not reset the
> searcher. Hence, when we call indexDictionary after that, many entries that
> are already in the stale searcher will not be indexed.
> Also, I see that IndexReader reader is used for the sole purpose of obtaining
> the docFreq of a given term in exist() function. This functionality can also
> be obtained by using just the searcher by calling searcher.docFreq. Thus, can
> we get away completely with reader and code associated with it like
> if (IndexReader.isLocked(spellIndex)){
> IndexReader.unlock(spellIndex);
> }
> and the reader related code in finalize?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
