[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945050#comment-14945050
]
Shalin Shekhar Mangar commented on SOLR-8131:
---------------------------------------------
bq. The current data_driven config doesn't have a schema.bak file
That's because the data driven config does not have a schema.xml and starts off
directly with a managed-schema file. The techproducts and basic configs example
do have a schema.xml (which I wasn't planning on removing) which will be
renamed to schema.xml.bak
bq. What about all the embedded documentation in the examples that disappears
on the first run with managed schema? Including all the commented-out sections
and "this is default" sections.
Good point, Alexandre. What do you think we should do? Maybe we can create a
page in the ref guide which has all that information instead? Another option
(don't know how feasible it'd be) is to have a describe mode in the /schema API
which prints helpful documentation about every enabled option/plugin in the
schema?
> 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: Trunk, 5.4
>
>
> 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]
