[
https://issues.apache.org/jira/browse/SOLR-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938319#comment-15938319
]
Ishan Chattopadhyaya commented on SOLR-6736:
--------------------------------------------
I thought about that, and decided to fail at the loading time instead of
execution time. The reason was that I think that it is better for a user to
know upfront that the collection, as uploaded through the configset API, won't
work as desired. Not failing at the collection creation time could mislead the
user into believing everything went fine, but his queries/updates would fail
much later.
bq. the core fails to load and the user won't know why it was not loaded
Towards this, I've added the following exception message that would be thrown
when the collection creation fails.
{code}
The configset for this collection was uploaded without any authentication in
place, and this operation is not available for collections with untrusted
configsets. To have this feature, re-upload the configset after enabling
authentication and authorization.
{code}
Do you think that makes sense?
> 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: [email protected]
For additional commands, e-mail: [email protected]
