[
https://issues.apache.org/jira/browse/LUCENE-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera resolved LUCENE-5320.
--------------------------------
Resolution: Fixed
Fix Version/s: 4.7
5.0
Assignee: Shai Erera
Lucene Fields: New,Patch Available (was: New)
Committed to trunk and 4x.
> Create SearcherTaxonomyManager over Directory
> ---------------------------------------------
>
> Key: LUCENE-5320
> URL: https://issues.apache.org/jira/browse/LUCENE-5320
> Project: Lucene - Core
> Issue Type: New Feature
> Components: modules/facet
> Reporter: Shai Erera
> Assignee: Shai Erera
> Fix For: 5.0, 4.7
>
> Attachments: LUCENE-5320.patch
>
>
> SearcherTaxonomyManager now only allows working in NRT mode. It could be
> useful to have an STM which allows reopening a SearcherAndTaxonomy pair over
> Directories, e.g. for replication. The problem is that if the thread that
> calls maybeRefresh() is not the one that does the commit(), it could lead to
> a pair that is not synchronized.
> Perhaps at first we could have a simple version that works under some
> assumptions, i.e. that the app does the commit + reopen in the same thread in
> that order, so that it can be used by such apps + when replicating the
> indexes, and later we can figure out how to generalize it to work even if
> commit + reopen are done by separate threads/JVMs.
> I'll see if SearcherTaxonomyManager can be extended to support it, or a new
> STM is required.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
