[
https://issues.apache.org/jira/browse/SOLR-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050032#comment-16050032
]
David Smiley commented on SOLR-10887:
-------------------------------------
+1 ! This has been an annoyance of mine.
[~arafalov] had some fantastic comments on this in another issue that I will
quote:
bq. On xml extension for managed-schema. Not having an XML extension means that
file is a special case everywhere. Admin UI had several JIRAs because that file
would not display properly, file system sorting is confusing, presentations
that try to explain things are confusing. Even just viewing the example schemas
on filesystem is confusing as there is no data-type mapping and editors do not
open it up without explicit intervention.
> Add .xml extension to managed-schema
> ------------------------------------
>
> Key: SOLR-10887
> URL: https://issues.apache.org/jira/browse/SOLR-10887
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Priority: Blocker
> Fix For: master (7.0)
>
>
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
