lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-9526) data_driven configs defaults to "strings" for unmapped fields, makes most fields containing "textual content" unsearchable, breaks tutorial examples
Date Thu, 06 Oct 2016 17:07:20 GMT

    [ https://issues.apache.org/jira/browse/SOLR-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15552529#comment-15552529
] 

Hoss Man commented on SOLR-9526:
--------------------------------

bq. Hoss Man why did you propose both docValues=true and indexed=true for {{\*_str}}?

I don't remember concretely, but I'm guessing my thinking was:

* (inherit) docValues=true (from the fieldType) so we get the most efficient faceting
* indexed=true so we can get the most efficient filtering
* stored=false because this is a redundant copy of another field that's already stored
* useDocValuesAsStored=false for the same reason.

bq. Also, it is unfortunate to split your "schema" across the schema file and a solrconfig
URP. Take the example where you want to use data driven schema, ...

I think he 1st priority should be making the data_driven configs work well for trivial examples
and the tutorial - by the time a user starts thinking about explicit fields they wnat, and
explicit copy/clones they want, they should be thinking about overridding/eliminating/disabling
all of the "schemaless" features anyway.

> 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.
> ----
> Original thread: http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201609.mbox/%3CCAC-n2zRPsspfnK43AGeCspchc5b-0FF25xLfnzogYuVyg2dWbw@mail.gmail.com%3E



--
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


Mime
View raw message