[
https://issues.apache.org/jira/browse/SOLR-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Neulinger updated SOLR-5626:
-----------------------------------
Labels: api collections rest zkcli.sh zookeeper (was: )
> Would like to be able to 'upconfig' and 'linkconfig' via collections api
> ------------------------------------------------------------------------
>
> Key: SOLR-5626
> URL: https://issues.apache.org/jira/browse/SOLR-5626
> Project: Solr
> Issue Type: Wish
> Components: SolrCloud
> Reporter: Nathan Neulinger
> Labels: api, collections, rest, zkcli.sh, zookeeper
>
> Right now, the collections API isn't self contained - to do server
> administration, you still have to externally use the zkCli.sh scripts to
> upload configs.
> It would be really nice to be able to issue a collections API call to upload
> a configuration and link that config. I realize that this providing a direct
> layer into Zk, but the benefit is that at that point - Zk could be completely
> hidden and behind the scenes - and only exposed to Solr itself.
> I would suggest that it take a file upload, examples:
> /solr/admin/collections
> action=UPCONFIG
> configName=whatevername
> configSolrHome=whateverpath
> configContent=fileUpload/multipart
> configContentType=typeOfUpload(mimetype?)
> /solr/admin/collections
> action=LINKCONFIG
> collection=collname
> configName=whatevername
> You could even extend the CREATE operation/api to take configContent and
> configContentType file upload, and dynamically create a configName. Then
> creating a collection becomes a one-shot API call with no outside
> dependencies.
> I would suggest that the zip/tar content be specified as rooted at the based
> of the config dir.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
