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

ASF subversion and git services commented on SOLR-10237:
--------------------------------------------------------

Commit 3b660018457234387558ff626c8b95bb6f4ce853 in lucene-solr's branch 
refs/heads/master from Tomas Fernandez Lobbe
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=3b66001 ]

SOLR-10237: Poly-Fields should work with subfield that have docValues=true


> Poly-Fields should work with subfield that have docValues=true
> --------------------------------------------------------------
>
>                 Key: SOLR-10237
>                 URL: https://issues.apache.org/jira/browse/SOLR-10237
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Tomás Fernández Löbbe
>         Attachments: SOLR-10237.patch, SOLR-10237.patch, 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 {{PointField}}. With 
> {{\[Int/Long/Float/Double/Date\]PointField}} 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