Andreas Hubold created SOLR-10118:
-------------------------------------
Summary: Wrong comments in example schema about DocValues
requirements
Key: SOLR-10118
URL: https://issues.apache.org/jira/browse/SOLR-10118
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: examples
Affects Versions: 6.4.1
Reporter: Andreas Hubold
Priority: Trivial
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:
{noformat}
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.
-->
{noformat}
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
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
