[
https://issues.apache.org/jira/browse/SOLR-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065940#comment-16065940
]
Varun Thacker commented on SOLR-10329:
--------------------------------------
Hi Alexandre,
I am looking at the new {{_default}} configset and see that we can make
improvements to make it shorter and copy edit stuff
For example, this comment is 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)
{code}
Another example, do we need a dynamic field for currency ?
{code}
<dynamicField name="*_c" type="currency" indexed="true" stored="true"/>
{code}
Should we create a specific Jira for this as this Jira title mentions all
examples ? Or should we limit the scope of this Jira?
> Rebuild Solr examples
> ---------------------
>
> Key: SOLR-10329
> URL: https://issues.apache.org/jira/browse/SOLR-10329
> Project: Solr
> Issue Type: Wish
> Components: examples
> Reporter: Alexandre Rafalovitch
> Labels: gsoc2017
>
> Apache Solr ships with a number of examples. They evolved from a kitchen sync
> example and are rather large. When new Solr features are added, they are
> often shoehorned into the most appropriate example and sometimes are not
> represented at all.
> Often, for new users, it is hard to tell what part of example is relevant,
> what part is default and what part is demonstrating something completely
> different.
> It would take significant (and very appreciated) effort to review all the
> examples and rebuild them to provide clean way to showcase best practices
> around base and most recent features.
> Specific issues are around kitchen sync vs. minimal examples, better approach
> to "schemaless" mode and creating examples and datasets that allow to create
> both "hello world" and more-advanced tutorials.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
