lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ishan Chattopadhyaya (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-6736) A collections-like request handler to manage solr configurations on zookeeper
Date Thu, 23 Mar 2017 15:07:42 GMT

    [ https://issues.apache.org/jira/browse/SOLR-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938533#comment-15938533
] 

Ishan Chattopadhyaya commented on SOLR-6736:
--------------------------------------------

Even if a component is loaded lazily, throwing an exception at the time of initialization
seems better than initializing the component without errors and throwing errors at the time
of the request. That way, we throw the exception as soon as possible technically. It will
just prevent surprises for the user, say during a production deployment, whereby the requests
would be guaranteed to be executed as desired if the initialization has succeeded.

One of the vulnerable plugins, RunExecutableListener, is usually executed during a commit.
An exception during a commit could lead to potential data loss. At least for that plugin (and
for every other vulnerable plugin as well), I'd prefer if the user got the error during the
initialization.

What do you think?

> A collections-like request handler to manage solr configurations on zookeeper
> -----------------------------------------------------------------------------
>
>                 Key: SOLR-6736
>                 URL: https://issues.apache.org/jira/browse/SOLR-6736
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>            Reporter: Varun Rajput
>            Assignee: Ishan Chattopadhyaya
>         Attachments: newzkconf.zip, newzkconf.zip, SOLR-6736-newapi.patch, SOLR-6736-newapi.patch,
SOLR-6736-newapi.patch, SOLR-6736.patch, SOLR-6736.patch, SOLR-6736.patch, SOLR-6736.patch,
SOLR-6736.patch, SOLR-6736.patch, SOLR-6736.patch, SOLR-6736.patch, SOLR-6736.patch, SOLR-6736.patch,
SOLR-6736.patch, test_private.pem, test_pub.der, zkconfighandler.zip, zkconfighandler.zip
>
>
> Managing Solr configuration files on zookeeper becomes cumbersome while using solr in
cloud mode, especially while trying out changes in the configurations. 
> It will be great if there is a request handler that can provide an API to manage the
configurations similar to the collections handler that would allow actions like uploading
new configurations, linking them to a collection, deleting configurations, etc.
> example : 
> {code}
> #use the following command to upload a new configset called mynewconf. This will fail
if there is alredy a conf called 'mynewconf'. The file could be a jar , zip or a tar file
which contains all the files for the this conf.
> curl -X POST -H 'Content-Type: application/octet-stream' --data-binary @testconf.zip
http://localhost:8983/solr/admin/configs/mynewconf?sig=<the-signature>
> {code}
> A GET to http://localhost:8983/solr/admin/configs will give a list of configs available
> A GET to http://localhost:8983/solr/admin/configs/mynewconf would give the list of files
in mynewconf



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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


Mime
View raw message