[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020835#comment-15020835
]
Varun Thacker commented on SOLR-8131:
-------------------------------------
The way ManagedSchemaFactory initializes itself is that it looks for the
default schema file ( "managed-schema" ) .
If it's not present then it takes the specified schema-name.xml ( default is
schema.xml ) and renames it to a file called managed-schema or to a name
explicitly mentioned.
We have lots of solrconfigs and schema files in a common directory and each
test can use any combination of that. Since we need to specify the new
managed-schema file name in the solrconfig file and that a test can use any
combination we can't manually change anything either.
I don't see a way where we can have multiple schema/solrconfig files in the
same directory and support any renaming logic from ManagedSchemaFactory
> 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
>
> Attachments: SOLR-8131.patch
>
>
> 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]
