[
https://issues.apache.org/jira/browse/SOLR-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-6913:
-----------------------------
Attachment: SOLR-6913-trim-schema.patch
Patch to the data-driven-schema-configs's {{schema.xml}} that removes the
following:
# {{binary}} field type
# All currency-related dynamic fields and field types
# All geo-related dynamic fields and field types
# All text field types and associated dynamic fields except {{string}} and
{{text_general}}, specifically all language-specific field types.
# All plural field types (these just add {{multiValued="true"}} to the
corresponding singular field types - this can instead be done on individual
fields where necessary).
# The {{random}} field type and {{random_\*}} dynamic field - these are for
sorting, but the data-driven example produces fields that are multi-valued, and
so not sortable.
This leaves a lot of dynamic fields, but since these are complementary to
managed schema, I'd like to leave them in.
Left to do:
# Remove the {{lang/}} directory and its contents
# Remove {{protwords.txt}} (unused)
# Switch to managed stopwords and synonyms
> audit & cleanup "schema" in data_driven_schema_configs
> ------------------------------------------------------
>
> Key: SOLR-6913
> URL: https://issues.apache.org/jira/browse/SOLR-6913
> Project: Solr
> Issue Type: Task
> Reporter: Hoss Man
> Assignee: Steve Rowe
> Priority: Blocker
> Fix For: 5.0
>
> Attachments: SOLR-6913-trim-schema.patch
>
>
> the data_driven_schema_configs configset has some issues that should be
> reviewed carefully & cleaned up...
> * currentkly includes a schema.xml file:
> ** this was previously pat of the old example to show the automatic
> "bootstraping" of schema.xml -> managed-schema, but at this point it's just
> kind of confusing
> ** we should just rename this to "managed-schema" in svn - the ref guide
> explains the bootstraping
> * the effective schema as it currently stands includes a bunch of copyFields
> & dynamicFields that are taken wholesale from the techproducts example
> ** some of these might make sense to keep in a general example (ie: "\*_txt")
> but in general they should all be reviewed.
> ** a bunch of this cruft is actually commented out already, but anything we
> don't want to keep should be removed to eliminate confusion
> * SOLR-6471 added an explicit "_text" field as the default and made it a
> copyField catchall (ie: "\*")
> ** the ref guide schema API example responses need to reflect the existence
> of this field:
> https://cwiki.apache.org/confluence/display/solr/Schemaless+Mode
> ** we should draw heavy attention to this field+copyField -- both with a "/!\
> NOTE" in the refguide and call it out in solrconfig.xml & "managed-schema"
> file comments since people who start with these configs may be suprised and
> wind up with a very bloated index
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
