[ 
https://issues.apache.org/jira/browse/SOLR-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14271547#comment-14271547
 ] 

Steve Rowe commented on SOLR-6913:
----------------------------------

bq. The main issue is that OOTB, this is the default and it thus leaves us 
pretty underpowered for an OOTB experience. 

Okay, I'll buy it: since {{data_driven_schema_configs}} is the default 
configset when creating a core or a collection from {{bin/solr}}, broad field 
type and dynamic field support is called for.

In addition to putting back the geo related and currency dynamic fields and 
field types, I'll put back the lang-specific field types, and add (previously 
missing) dynamic fields for them.

> 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, Trunk
>
>         Attachments: SOLR-6913-trim-schema.patch, 
> SOLR-6913-trim-schema.patch, SOLR-6913.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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to