Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <1037224028.1242628367415.JavaMail.jira@brutus>
Date: Sun, 17 May 2009 23:32:47 -0700 (PDT)
From: "Nicolas Pastorino (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1147) QueryElevationComponent : updating
 elevate.xml through HTTP
In-Reply-To: <917997570.1241613270657.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710285#action_12710285 ] 

Nicolas Pastorino commented on SOLR-1147:
-----------------------------------------

It indeed sounds like a potentially more generic feature. Should this end-up in dedicated request Handler, which receives as parameters :
* the name of the concerned searchComponent, or other 'module' using a configuration file
* the updated configuration

And passes along the updated configuration to the concerned 'module' in some way ? Should an existing interface be extended in order to comprize the necessary methods, or should this be handled with inheritance here, an abstract class presenting the 'updateConfiguration( ... )' method ? There probably are quite a few other approaches on this.

Thanks for your participation to this !

> QueryElevationComponent : updating elevate.xml through HTTP
> -----------------------------------------------------------
>
>                 Key: SOLR-1147
>                 URL: https://issues.apache.org/jira/browse/SOLR-1147
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 1.3, 1.4, 1.5
>         Environment: Any
>            Reporter: Nicolas Pastorino
>            Priority: Minor
>         Attachments: QueryElevationAdministrationRequestHandler.java, QueryElevationAdministrationRequestHandler.java
>
>
> If one wants to update the configuration file for the QueryElevationComponent, direct edition of the file is mandatory. Currently the process seems to be : 
> # Replace elevate.xml in Solr's dataDir
> # Commit. It appears that when having elevate.xml in Solr's dataDir, and solely in this case, commiting triggers a reload of elevate.xml. This does not happen when elevate.xml is stored in Solr's conf dir.
> As a system using Solr, i would find handy to be able to push an updated elevate.xml file/XML through HTTP, with an automatic reload of it. This would remove the currently mandatory requirement of having a direct access to the elevate.xml file, allowing more distributed architectures. This would also increase the Query Elevation system's added value by making it dynamic, configuration-wise.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.