Return-Path: 
 <solr-dev-return-18330-apmail-lucene-solr-dev-archive=lucene.apache.org@lucene.apache.org>
Delivered-To: apmail-lucene-solr-dev-archive@minotaur.apache.org
Received: (qmail 39925 invoked from network); 29 Jul 2009 08:00:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 29 Jul 2009 08:00:44 -0000
Received: (qmail 8292 invoked by uid 500); 29 Jul 2009 08:00:44 -0000
Delivered-To: apmail-lucene-solr-dev-archive@lucene.apache.org
Received: (qmail 8213 invoked by uid 500); 29 Jul 2009 08:00:44 -0000
Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:solr-dev-help@lucene.apache.org>
List-Unsubscribe: <mailto:solr-dev-unsubscribe@lucene.apache.org>
List-Post: <mailto:solr-dev@lucene.apache.org>
List-Id: <solr-dev.lucene.apache.org>
Reply-To: solr-dev@lucene.apache.org
Delivered-To: mailing list solr-dev@lucene.apache.org
Received: (qmail 8002 invoked by uid 99); 29 Jul 2009 08:00:44 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2009 08:00:44 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2009 08:00:41 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 929B0234C051
	for <solr-dev@lucene.apache.org>; Wed, 29 Jul 2009 01:00:19 -0700 (PDT)
Message-ID: <1353350315.1248854419599.JavaMail.jira@brutus>
Date: Wed, 29 Jul 2009 01:00:19 -0700 (PDT)
From: "Noble Paul (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Issue Comment Edited: (SOLR-1307) Provide a standard way to
 reload plugins
In-Reply-To: <939735083.1248329954880.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ 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.