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

Wrong comments in example schema about DocValues requirements

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

Details

    • Bug
    • Status: Resolved
    • Trivial
    • Resolution: Fixed
    • 6.4.1
    • None
    • examples
    • None

    Description

      Comments in the example schema files of Solr about field
      requirements for DocValues seem to be wrong. For example, in
      server/solr/configsets/basic_configs/conf/managed-schema:

           docValues: [...] they might
              require the field to be single-valued, be required or have a default
              value (check the documentation of the field type you're
      interested in
              for more information)
      
           <!-- The StrField [...]
              It supports doc values but in that case the field needs to be
              single-valued and either required or have a default value.
             -->
      
         <!--
           Default numeric field types. [...]
      
           These fields support doc values, but they require the field to be
           single-valued and either be required or have a default value.
         -->
      

      I haven't found these limitations in the reference guide. It states that
      multi-valued DocValues are stored as SORTED_SET.

      The comments are probably outdated?

      It seems the restrictions have been removed, e.g. with SOLR-4490 and https://github.com/apache/lucene-solr/commit/d208878c116bb66d6cb114ce51f69b7264ab668a#diff-ecbdc5fb2ccf861a92837e21fb37ace8

      Attachments

        Activity

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

          People

            Unassigned Unassigned
            ahubold Andreas Hubold
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment