[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948377#comment-14948377
]
Varun Thacker commented on SOLR-8131:
-------------------------------------
bq. 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
I don't think thats a good idea. We might end up having the same issue we had
with collection1 .
If ManagedIndexSchemaFactory is by default we can have the schema editor thats
in your plan without any problems?
> 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]
