You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Nicolas Pastorino (JIRA)" <ji...@apache.org> on 2009/05/06 14:48:32 UTC
[jira] Updated: (SOLR-1147) QueryElevationComponent : updating
elevate.xml through HTTP
[ https://issues.apache.org/jira/browse/SOLR-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Pastorino updated SOLR-1147:
------------------------------------
Attachment: QueryElevationAdministrationRequestHandler.java
The attached RequestHandler could be a solution to the problematic presented above. Please note that the API usage may be awkward, as well as the way Java is leveraged. That's my first Solr extension :) And yes, there are quite a few unresolved things, spottable through the _'TODO'_ and _'FIXME'_ annotations.
It was tested against Solr's trunk, and seems to be working. The new Elevate configuration is to be passed, as an XML string, in the "elevate-configuration" request parameter.
> 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
>
>
> 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.