[
https://issues.apache.org/jira/browse/SOLR-10967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072611#comment-16072611
]
Jason Gerlowski commented on SOLR-10967:
----------------------------------------
{code}
+
For more information, on how to customize this file, please see
- http://wiki.apache.org/solr/SchemaXml
+
http://lucene.apache.org/solr/guide/6_6/documents-fields-and-schema-design.html
+ //nocommit: How can we point to the latest and not make it version specific?
{code}
The URL
"http://lucene.apache.org/solr/guide/documents-fields-and-schema-design.html";
will redirect you to that page in the latest published ref-guide version, so it
might be a good way around the issue you raised there.
OTOH, having the version hardcoded in the schema reminds us to verify that the
page referenced actually exists. If we rely on a "latest"-based redirect, we
would never notice if {{document-fields-and-schema-design.html}} goes away due
to unrelated doc changes. (I'm still in favor of making use of the redirect
mentioned above, just wanted to mention this in case others think this is a big
deal)
> Cleanup the default configset
> -----------------------------
>
> Key: SOLR-10967
> URL: https://issues.apache.org/jira/browse/SOLR-10967
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: master (7.0)
> Reporter: Varun Thacker
> Assignee: Varun Thacker
> Attachments: SOLR-10967.patch
>
>
> The schema in the default configset is 1000 lines . We should audit it and
> see if we can prune it a little bit.
> Also in this Jira we should fix some of the copy editing . For example,
> comments like these are outdated
> {code}
> This is the Solr schema file. This file should be named "schema.xml" and
> should be in the conf directory under the solr home
> (i.e. ./solr/conf/schema.xml by default)
> or located where the classloader for the Solr webapp can find it.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
