[
https://issues.apache.org/jira/browse/SOLR-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987632#comment-15987632
]
Alexandre Rafalovitch commented on SOLR-10574:
----------------------------------------------
I had an idea (in some other JIRA) that we have a kitchen-sync schema with some
Admin-UI extra that allows to push any of its own definitions to a different
schema via managed API. So, when you want to add Armenian field type, you load
up/create collection with that schema, open it up on the Admin UI, and then
push the definition to your primary collection. Then, the config collection can
be deleted again.
I have not tested if it is possible. The main issue is generating API
configuration format as well as Admin-UI glue (which could be similar to
/browse).
> Choose a default configset for Solr 7
> -------------------------------------
>
> Key: SOLR-10574
> URL: https://issues.apache.org/jira/browse/SOLR-10574
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
>
> Currently, the data_driven_schema_configs is the default configset when
> collections are created using the bin/solr script and no configset is
> specified.
> However, that may not be the best choice. We need to decide which is the best
> choice, out of the box, considering many users might create collections
> without knowing about the concept of a configset going forward.
> (See also SOLR-10272)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
