You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/09/16 12:44:00 UTC
[jira] [Commented] (SOLR-10887) Add .xml extension to
managed-schema
[ https://issues.apache.org/jira/browse/SOLR-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416090#comment-17416090 ]
ASF subversion and git services commented on SOLR-10887:
--------------------------------------------------------
Commit df903cbdc1de7fb2c3469b9773d6f9d23d591a5d in solr's branch refs/heads/main from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=df903cb ]
SOLR-10887: Append .xml to managed-schema file VERSION 2 (#279)
Managed schema file is now called "managed-schema.xml", however there is a fallback to "managed-schema" since that is a common legacy name for the file. Updated the name of the files used in running tests.
> Add .xml extension to managed-schema
> ------------------------------------
>
> Key: SOLR-10887
> URL: https://issues.apache.org/jira/browse/SOLR-10887
> Project: Solr
> Issue Type: Sub-task
> Components: Schema and Analysis
> Reporter: Ishan Chattopadhyaya
> Assignee: David Eric Pugh
> Priority: Major
> Time Spent: 7h 10m
> Remaining Estimate: 0h
>
> Discussions here SOLR-10574.
> There is consensus to renaming managed-schema back to managed-schema.xml. Requires backcompat handling as mentioned in Yonik's comment:
> {code}
> there is back compat to consider. I'd also prefer that if it get changed, we first look for "managed-schema.xml", then "managed-schema", and then "schema.xml" to preserve back compat.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org