[ 
https://issues.apache.org/jira/browse/SOLR-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Høydahl closed SOLR-1147.
-----------------------------
    Resolution: Won't Fix

Closing ancient issue. Now superseded by e.g. pushing files to ZK and various 
managed filters through REST.

> Updating configuration files 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
>
>
> *Current behaviour* :
> If one wants to update a configuration file placed in Solr's conf dir, direct 
> edition of the file is mandatory. Currently the process is : 
> # Replace the concerned configuration file in Solr's conf dir
> # Commit.
> A commit triggers a reload of the configurations files, as long as their 
> associated components are registered to this event. This can be achieved for 
> a searchComponent as follows : 
> {noformat}
>     <str name="refreshOnCommmit">true</str> 
> {noformat}
> _Side question : how to register other types of components to the commit 
> event ?_
> *Use case* :
> As a system using Solr, i would find handy to be able to push an updated 
> configuration file through HTTP.
> This would remove the currently mandatory requirement of having a direct 
> access to configuration files, allowing more distributed architectures. This 
> would also increase the components' added value by making them dynamic, 
> configuration-wise.
> *Possible design* :
> A new requestHandler, taking as parameter : 
> * the name of the file to update
> * optionnally if a backup of the previous version of the file is to be done ( 
> cf replicationHandler )
> *Open questions* :
> * Should reloading the new configuration keep using the "reload on commit" 
> feature ? 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to