[
https://issues.apache.org/jira/browse/SOLR-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266114#comment-14266114
]
Erik Hatcher commented on SOLR-6913:
------------------------------------
And changing all those plural field types mentioned in solrconfig to singular,
this is what happens on {{bin/post films example/films/films.json}}:
{code}
LucidErikMBP:solr erikhatcher$ bin/post films example/films/films.json
INFO - 2015-01-06 13:45:08.001; org.apache.solr.schema.ManagedIndexSchema;
Upgraded to managed schema at
/Users/erikhatcher/dev/trunk/solr/server/solr/films/conf/managed-schema
INFO - 2015-01-06 13:45:08.041;
org.apache.solr.update.processor.LogUpdateProcessor; [films] webapp=/solr
path=/update params={} {add=[/en/001 (1489556637456793600)]} 0 75
ERROR - 2015-01-06 13:45:08.042; org.apache.solr.common.SolrException;
org.apache.solr.common.SolrException: ERROR: [doc=/en/45_2006] multiple values
encountered for non multiValued field genre: [Black comedy, Thriller,
Psychological thriller, Indie film, Action Film, Crime Thriller, Crime Fiction,
Drama]
{code}
:/ - now what? We need the auto-field guessing to also guess and set
multiValued, seems like.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
