[
https://issues.apache.org/jira/browse/SOLR-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710312#action_12710312
]
Nicolas Pastorino commented on SOLR-1147:
-----------------------------------------
Simpler, indeed. Lower-level.
Should some versioning and/or backup on configuration files be implemented too ?
On the software-design part of it : should this be a plain requestHandler ?
I propose myself for being the "little hands" coding this, if this is
acceptable for all of you, after all design points are sorted out of course.
> 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.
