[ https://issues.apache.org/jira/browse/SOLR-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15497815#comment-15497815 ]
Hoss Man commented on SOLR-9526: -------------------------------- I have no idea if other parts of the tutorial are totally broken, but my biggest question first and foremost is WTF is up with "strings" being the defaultFieldType in data_driven_schema_configs???? that makes no sense to me at all. It appears it's been that way since commit 0ff1e75b for SOLR-6779, but there's no explanation i can see in that jira as to why this change was made. Has this really been broken this horiffically since 5.0?!?!?! > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org