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

Erick Erickson commented on SOLR-4026:
--------------------------------------

I don't quite understand what you mean here. Are you talking about the CREATE 
action on cores admin? And by "add schema configuration parameters to the URL", 
do you mean modify an existing schema somehow or stream up one you have locally?

I can see where streaming up your local schema.xml (that you'd customized) 
would be useful, but..... to have a complete solution that would allow you to 
_completely_ create a new instance without having already having at least a 
<newcollection>/conf directory in place, you'd also have to provide a way to 
put all the _other_ conf files that you needed up on your server. Stopwords, 
solrconfig.xml, mapping files, synonyms, even, admin_extra.html.

This problem seems like something that would be very awkward to solve in Solr 
via a URL, it seems like an infrastructure that needed to do something like 
this would be better off scripting putting the conf directory "the right place" 
then using CREATE as it stands now....
                
> Create a custom schema with creating collection
> -----------------------------------------------
>
>                 Key: SOLR-4026
>                 URL: https://issues.apache.org/jira/browse/SOLR-4026
>             Project: Solr
>          Issue Type: Wish
>    Affects Versions: 4.0
>            Reporter: milesli
>
> It seems like we can not create custom schema for different collection,
> if we can  add schema configuration parameters to url of creating collection, 
> that's better.
> thanks.

--
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]

Reply via email to