[ 
https://issues.apache.org/jira/browse/SOLR-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900293#comment-15900293
 ] 

David Smiley commented on SOLR-10237:
-------------------------------------

Oh I see; thanks for the explanation.

bq. Another option is to start supporting DV in the coordinates by creating the 
DV fields when requested, they could be used as you said when ValueSource is 
needed, probably inheriting the configuration (docValues=true/false) from the 
PointType field?

I think this is the path forward.  Doing anything else is worse -- why 
_shouldn't_ we let users use DocValues for purposes that DocValues were created 
for?

As a related aside... I'm wondering if we may want to deprecate/remove the 
singular {{SchemaField.createField}} and simply have all field types do their 
logic in one method {{createFields}}.  Perhaps further, it might accept the 
Lucene {{Document}} as a destination to thus avoid some needless {{Field[]}} 
creation.  If you agree, the method might then be named {{addFieldsToDoc}}.  
I'm bumping into this a bit as I contemplate a TextField that can optionally 
put it's stored value embedded in a separate (compressed) BinaryDocValuesField 
-- SOLR-10117.

> Poly-Fields should error if subfield has docValues=true
> -------------------------------------------------------
>
>                 Key: SOLR-10237
>                 URL: https://issues.apache.org/jira/browse/SOLR-10237
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Tomás Fernández Löbbe
>            Priority: Minor
>         Attachments: SOLR-10237.patch
>
>
> DocValues aren’t really supported in poly-fields at this point, but they 
> don’t complain if the schema definition of the subfield has docValues=true. 
> This leaves the index in an inconsistent state, since the SchemaField has 
> docValues=true but there are no DV for the field.
> Since this breaks compatibility, I think we should just emit a warning unless 
> the subfield is an instance of {{PointType}}. With 
> {{\[Int/Long/Float/Double/Date\]PointType}} subfields, this is particularly 
> important, since they use {{IndexOrDocValuesQuery}}, that would return 
> incorrect results.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to