[SOLR-9526] data_driven configs defaults to "strings" for unmapped fields, makes most fields containing "textual content" unsearchable, breaks tutorial examples

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 7.0, 7.1, 8.0
• Component/s: UpdateRequestProcessors
• Labels: dynamic-schema
• Assignee: Jan Høydahl
• Reporter: Chris M. Hostetter
• Created: 17/Sep/16 00:26
• Updated: 08/Jun/19 15:29
• Resolved: 06/Jul/17 14:56

Description

James Pritchett pointed out on the solr-user list that this sample query from the quick start tutorial matched no docs (even though the tutorial text says "The above request returns only one document")...

http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=name:foundation

The root problem seems to be that the add-unknown-fields-to-the-schema chain in data_driven_schema_configs is configured with...

<str name="defaultFieldType">strings</str>

...and the "strings" type uses StrField and is not tokenized.

---

Original thread: http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201609.mbox/[e-mail]%3E

Issue Links

• is duplicated by: SOLR-8495 Schemaless mode cannot index large text fields
• is duplicated by: SOLR-6966 For Data Driven Schema, consider multi-word text fields to be text, not string field types
• is related to: SOLR-8495 Schemaless mode cannot index large text fields
• relates to: SOLR-6966 For Data Driven Schema, consider multi-word text fields to be text, not string field types
• relates to: SOLR-6871 Need a process for updating & maintaining the new quickstart tutorial (and any other tutorials added to the website)
• links to: GitHub Pull Request #91