You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2015/03/01 01:35:04 UTC

[jira] [Closed] (SOLR-4026) Create a custom schema with creating collection

     [ https://issues.apache.org/jira/browse/SOLR-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shawn Heisey closed SOLR-4026.
------------------------------
    Resolution: Won't Fix

[~sezelee], some of the functionality you want is currently available.  There are managed APIs for adding fields to the schema, editing stopwords, and editing synonyms.

https://cwiki.apache.org/confluence/display/solr/Schema+API
https://cwiki.apache.org/confluence/display/solr/Managed+Resources

Once Solr is a standalone app that has complete control of the network and HTTP layers, full configuration management will be possible to implement securely.  That will be one of the things that gets looked at first.

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org