[
https://issues.apache.org/jira/browse/SOLR-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated SOLR-4872:
-----------------------------------
Description:
I have a need, in an TokenizerFactory or TokenFilterFactory, to have a shared
cache that is cleaned up when the core is torn down.
There is no 'close' protocol on these things, and Solr rejects analysis
components that are SolrCoreAware.
Possible solutions:
# add a close protocol to these factories and make sure it gets called at core
shutdown.
# allow these items to be 'core-aware'.
# invent some notion of 'schema-lifecycle-aware'.
was:
I have a need, in an TokenizerFactory or TokenFilterFactory, to have a shared
cache that is cleaned up when the core is torn down. Solr rejects analysis
components that are SolrCoreAware. Is there some really good reason for this?
What harm would come from allowing one to register a CloseHook?
> Allow schema analysis object factories to be cleaned up properly when the
> core shuts down
> -----------------------------------------------------------------------------------------
>
> 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 TokenizerFactory or TokenFilterFactory, to have a shared
> cache that is cleaned up when the core is torn down.
> There is no 'close' protocol on these things, and Solr rejects analysis
> components that are SolrCoreAware.
> Possible solutions:
> # add a close protocol to these factories and make sure it gets called at
> core shutdown.
> # allow these items to be 'core-aware'.
> # invent some notion of 'schema-lifecycle-aware'.
--
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]
