[ https://issues.apache.org/jira/browse/LUCENE-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated LUCENE-3786: -------------------------------- Fix Version/s: (was: 4.1) 5.0 4.2 > Create SearcherTaxoManager > -------------------------- > > Key: LUCENE-3786 > URL: https://issues.apache.org/jira/browse/LUCENE-3786 > Project: Lucene - Core > Issue Type: New Feature > Components: modules/facet > Reporter: Shai Erera > Assignee: Shai Erera > Priority: Minor > Fix For: 4.2, 5.0 > > > If an application wants to use an IndexSearcher and TaxonomyReader in a > SearcherManager-like fashion, it cannot use a separate SearcherManager, and > say a TaxonomyReaderManager, because the IndexSearcher and TaxoReader > instances need to be in sync. That is, the IS-TR pair must match, or > otherwise the category ordinals that are encoded in the search index might > not match the ones in the taxonomy index. > This can happen if someone reopens the IndexSearcher's IndexReader, but does > not refresh the TaxonomyReader, and the category ordinals that exist in the > reopened IndexReader are not yet visible to the TaxonomyReader instance. > I'd like to create a SearcherTaxoManager (which is a ReferenceManager) which > manages an IndexSearcher and TaxonomyReader pair. Then an application will > call: > {code} > SearcherTaxoPair pair = manager.acquire(); > try { > IndexSearcher searcher = pair.searcher; > TaxonomyReader taxoReader = pair.taxoReader; > // do something with them > } finally { > manager.release(pair); > pair = null; > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org