[
https://issues.apache.org/jira/browse/SOLR-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681442#comment-13681442
]
Benson Margulies commented on SOLR-4872:
----------------------------------------
Here's a little more research. While it is possible to configure Solr to use a
particular Lucene analyzer, it's very undesirable. The usual thing is to use
the invisible (and final) TokenizerChain analyzer, which accepts the a
tokenizer and a list of filters. Since users want to mix-and-match tokenizers
and filters, it is not a good idea to supplant TokenizerChain with an Analyzer.
TokenizerChain does not override close(). The net result as far as I can see is
that there is no good way to control the reuseStrategy or otherwise get close()
behavior inside Solr.
> Allow analyzers to be SolrCoreAware
> -----------------------------------
>
> Key: SOLR-4872
> URL: https://issues.apache.org/jira/browse/SOLR-4872
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.3
> Reporter: Benson Margulies
>
> I have a need, in an analyzer, to have a shared cache that is cleaned up when
> the core is torn down. Solr rejects analyzer components that are
> SolrCoreAware. Is there some really good reason for this? What harm would
> come from allowing one to register a CloseHook?
--
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: [email protected]
For additional commands, e-mail: [email protected]
