[ 
https://issues.apache.org/jira/browse/SOLR-11306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Gerlowski updated SOLR-11306:
-----------------------------------
    Attachment: SOLR-11306.patch

Attached patch edits the matching comments in all schema files to just say:

{code}
<!-- The StrField type is not analyzed, but indexed/stored verbatim. -->
{code}

Tests and precommit pass.

> Solr example schemas inaccurate comments on  docValues and StrField
> -------------------------------------------------------------------
>
>                 Key: SOLR-11306
>                 URL: https://issues.apache.org/jira/browse/SOLR-11306
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: examples
>    Affects Versions: 6.6, 7.0
>            Reporter: Tom Burton-West
>            Priority: Minor
>         Attachments: SOLR-11306.patch
>
>
> Several of the example managed-schema files have an outdated comment about 
> docValues and StrField.  In Solr 6.6.0 these are under solr-6.6.0/solr/server 
> and the lines where the comment starts for each file are:
> solr/configsets/basic_configs/conf/managed-schema:216:   
> solr/configsets/data_driven_schema_configs/conf/managed-schema:221:    
> solr/configsets/sample_techproducts_configs/conf/managed-schema:317
> In the case of 
> Solr-6.6.0/server/solr/configsets/basic_configs/conf/managed-schema, shortly 
> after the comment  are some lines which seem to directly contradict the 
> comment:
> 216      <!-- The StrField type is not analyzed, but indexed/stored verbatim.
>    217         It supports doc values but in that case the field needs to be
>    218         single-valued and either required or have a default value.
>    219        -->
> On line 221 a StrField is declared with docValues that is multiValued:
> 221      <fieldType name="strings" class="solr.StrField" 
> sortMissingLast="true" multiValued="true" docValues="true" />
> Also note that the comments above say that the field must either be required 
> or have a default value, but line 221 appears to satisfy neither condition.
> The JavaDocs indicate that StrField can be multi-valued 
> https://lucene.apache.org/core/6_6_0//core/org/apache/lucene/index/DocValuesType.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to