[
https://issues.apache.org/jira/browse/SOLR-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569820#comment-13569820
]
Shawn Heisey commented on SOLR-4193:
------------------------------------
I'd like the ability to tell a collection to use a different config set. I
brought this up on the mailing list, where Mark Miller directed me to this
issue. Consider this situation, which is essentially where I am right now:
I have a config set named 'mbbasecfg' which for the immediate future will be
used by all collections that I add to my SolrCloud (4.1). Each collection will
get used by a SolrJ servlet, which serves content from one specific customer.
The 'mb' prefix is something specific to our software.
Let's say customer X decides they want things to work very differently for
their application, and they are willing to pay us development costs to make it
happen. Their requested changes will require a different Solr config and maybe
a different schema. Customer X already has a collection in SolrCloud.
What I'd like to be able to do is upload a new config set called mbcustxcfg,
then ask SolrCloud to change the customerx collection to use that new config
set. If the changes don't require a reindex, we'd be done after reloading the
collection. If they do require a reindex, then we'll do that.
Currently we would have to delete their collection and build it again with a
new config set. If renaming a collection is possible (not sure whether it is),
we could do that before making a new collection with the original name. This
is not the end of the world, of course.
> 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.2, 5.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
