lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Pastorino (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-1147) Updating configuration files through HTTP
Date Wed, 20 May 2009 14:40:45 GMT

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

Nicolas Pastorino updated SOLR-1147:
------------------------------------

    Description: 
*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 ? 

  was:
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.

        Summary: Updating configuration files through HTTP  (was: QueryElevationComponent
: updating elevate.xml through HTTP)

> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message