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

Eric Pugh commented on SOLR-4193:
---------------------------------

Doing some Jira gardening, and I think this ticket is dealt with, though in 
slightly different way...

Uploading individual configuration files and complete configsets is supported 
through bin/solr zk and the Configsets API. The remaining distinction from this 
proposal is automatically resolving a collection’s linked configset through a 
collection-relative upload endpoint.

In my mind though, I want us to think more about a configset as a first class 
citiizen, and not just the backer of a collection...   so not going through a 
collection endpoint ameks sense to me....

> A ZooKeeper RequestHandler that allows you to post config files to a 
> collections linked config set or a specific config set.
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-4193
>                 URL: https://issues.apache.org/jira/browse/SOLR-4193
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: 4.9, 6.0
>
>         Attachments: SOLR-4193.patch, SOLR-4193.patch
>
>
> Could have an admin zk handler and one per core?
> An admin zk handler would allow you to access it without specifying an 
> existing core if done right.
> One per core lets you do things like:
> post solrconfig.xml to localhost:8983:/solr/collection1/zkhandler
> Then we look up what config set we linked to and overwrite the solrconfig.xml.
> You can already GET config files through another handler, so at the moment 
> I'd avoid duplicating that.
> Could imagine adding commands over time though.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to