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

Upayavira commented on SOLR-8131:
---------------------------------

What I'd like to see is the techproducts sample stay the same (it has always 
been a static schema, let it stay that way), but update the bin/solr script (or 
such) to upload a standard managed schema config on first start up - or allow 
it via an argument:

bin/solr -conf managed start

That way, once the server is started, everything needed can be done via the UI.

I'd love to see this soon, as I want to use it in my talk at LuceneRevolution 
next week!! I'll also add basic "add field", "add dynamic field" and "copy 
field" support to the schema browser in time for that talk also :-)

What I'm saying is - there's no such thing as default configset anymore. What 
I'd suggest is that Solr starts with a single configset uploaded, which is in 
managed schema mode, or there is a very easy way to do it, on startup.


> Make ManagedIndexSchemaFactory as the default in Solr
> -----------------------------------------------------
>
>                 Key: SOLR-8131
>                 URL: https://issues.apache.org/jira/browse/SOLR-8131
>             Project: Solr
>          Issue Type: Wish
>          Components: Data-driven Schema, Schema and Analysis
>            Reporter: Shalin Shekhar Mangar
>              Labels: difficulty-easy, impact-high
>             Fix For: 5.4, Trunk
>
>
> The techproducts and other examples shipped with Solr all use the 
> ClassicIndexSchemaFactory which disables all Schema APIs which need to modify 
> schema. It'd be nice to be able to support both read/write schema APIs 
> without needing to enable data-driven or schema-less mode.
> I propose to change all 5.x examples to explicitly use 
> ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default 
> in trunk (6.x).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to