Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-12350

Do not use docValues as stored for _str (copy)fields in _default configset

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 7.5, 8.0
    • Data-driven Schema
    • None

    Description

      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

      <dynamicField name="*_str" type="strings" stored="false" docValues="true" indexed="false" />

      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 Chris M. Hostetter initially suggested, and explicitly set it to false starting from 7.4:

      <dynamicField name="*_str" type="strings" stored="false" indexed="false" docValues="true" useDocValuesAsStored="false" />
      

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            janhoy Jan Høydahl
            janhoy Jan Høydahl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment