You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2016/09/17 00:27:21 UTC
[jira] [Created] (SOLR-9526) data_driven configs defaults to
"strings" for unmapped fields, makes most fields containing "textual
content" unsearchable, breaks tutorial examples
Hoss Man created SOLR-9526:
------------------------------
Summary: data_driven configs defaults to "strings" for unmapped fields, makes most fields containing "textual content" unsearchable, breaks tutorial examples
Key: SOLR-9526
URL: https://issues.apache.org/jira/browse/SOLR-9526
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Hoss Man
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...
{code}
<str name="defaultFieldType">strings</str>
{code}
...and the "strings" type uses StrField and is not tokenized.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org