[
https://issues.apache.org/jira/browse/SOLR-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470337#comment-15470337
]
Alexandre Rafalovitch commented on SOLR-9487:
---------------------------------------------
Ok, I know what you are doing.
You created an instance first and then copied schema.xml into there. But Solr 6
uses managed schema and on first run *schema.xml* is converted into
*managed-schema* file. If you do that and *then* copy your schema.xml into the
directory it will be ignored.
So, either remove *managed-schema* file, copy yours and reload core, or -
probably better - create a new collection/core using the command I gave above.
*-d* flag points at your whole configuration directory and uses that as a
template.
> Solr 6.x ignores field name="type" in schema.xml
> ------------------------------------------------
>
> Key: SOLR-9487
> URL: https://issues.apache.org/jira/browse/SOLR-9487
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Schema and Analysis
> Affects Versions: 6.1
> Environment: Ubuntu 2.6.32-45-pve
> Reporter: Sorin Gheorghiu
> Labels: rsol, sunspot
> Attachments: Solr5.0_field_type.png
>
>
> In order to use the Ruby Sunspot gem, a customised schema.xml should be used
> [1]. The field "type" will exist in Solr 5.0 (in Schema Browser), but Solr 6.1
> <field name="type" stored="false" type="string" multiValued="true"
> indexed="true"/>
> As consequence, Sunspot will fail to seed data with the following error:
> RSolr::Error::Http: RSolr::Error::Http - 400 Bad Request
> Error: 'ERROR: [doc=Classification 1] unknown field \'type\'','code'=>400}}
> [1]
> https://github.com/sunspot/sunspot/tree/master/sunspot_solr/solr/solr/configsets/sunspot/conf
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]