[
https://issues.apache.org/jira/browse/SOLR-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736496#action_12736496
]
Noble Paul edited comment on SOLR-1307 at 7/29/09 12:59 AM:
------------------------------------------------------------
The possible events as I see are config file changes , commit /optimize.
commit/optimize are already handled . so the main requirement is to make it
possible for Solr to 'watch' a few files .
say
{code:java}
core.registerConfFileListener(listener, List<String> files);
{code}
this would need a new interface
{code:java}
public interface ConfFileListener {
public void confFileChanged(List<String> changedFiles);
}
{code}
was (Author: noble.paul):
The possible events as I see are config file changes , commit /optimize.
commit/optimize are already handled . so the main requirement is to make it
possible for Solr to 'watch' a few files .
say
{code:java}
core.registerConfFileListener(listener, List<String> files);
{code}
this would need a new interface
{code:java}
public interface ConfFileListener {
public void confFileChanged(List<String> files);
}
{code}
> Provide a standard way to reload plugins
> ----------------------------------------
>
> Key: SOLR-1307
> URL: https://issues.apache.org/jira/browse/SOLR-1307
> Project: Solr
> Issue Type: New Feature
> Components: search, update
> Reporter: Shalin Shekhar Mangar
> Fix For: 1.5
>
>
> Currently, Solr plugins have no standard way to reload themselves. Each
> plugin invents its own mechanism e.g. SpellCheckComponent. For others, even
> small changes to configuration files are visible only after a core reload.
> Examples include changing elevate.xml, stopwords.txt etc.
> We should provide a standard way for plugins to reload themselves on events
> relevant to them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
