You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jan Høydahl (JIRA)" <ji...@apache.org> on 2018/05/14 12:27:00 UTC

[jira] [Created] (SOLR-12350) Do not use docValues as stored for _str (copy)fields in _default configset

Jan Høydahl created SOLR-12350:
----------------------------------

             Summary: Do not use docValues as stored for _str (copy)fields in _default configset
                 Key: SOLR-12350
                 URL: https://issues.apache.org/jira/browse/SOLR-12350
             Project: Solr
          Issue Type: Improvement
      Security Level: Public (Default Security Level. Issues are Public)
          Components: Data-driven Schema
            Reporter: Jan Høydahl
             Fix For: 7.4, master (8.0)


When improving data-driven mode in SOLR-9526 we discussed back and forth whether to set {{useDocValuesAsStored}} for the {{*_str}} copy of text fields. This dynamic field is currently defined as
{code:xml}
<dynamicField name="*_str" type="strings" stored="false" docValues="true" indexed="false" />{code}
Having lived with the current setting since 7.0, I think it is too noisy to return all the _str fields since this is redundant content from the analysed original field. Thus I propose to do as [~hossman] initially suggested, and explicitly set it to false starting from 7.4:
{code:xml}
<dynamicField name="*_str" type="strings" stored="false" indexed="false" docValues="true" useDocValuesAsStored="false" />
{code}
Note that this does not change how things are stored, only whether to display these by default. The {{*_str}} fields will still be available for sorting, faceting etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org