[
https://issues.apache.org/jira/browse/SOLR-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604391#comment-13604391
]
Erick Erickson commented on SOLR-1147:
--------------------------------------
Being able to update _all_ the various configs without
1> having to restart Solr
2> editing through <insert favorite editor here>
would help with ease-of-use. Maybe the new admin UI could be enhanced to do
this?
> 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 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]
