[
https://issues.apache.org/jira/browse/SOLR-11532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216295#comment-16216295
]
David Smiley commented on SOLR-11532:
-------------------------------------
Ouch; this is a serious bug! If we can have {{useDocValuesAsStored}}=false
influence the optimization in SOLR-8344 then that would both fix this bug and
be something that makes sense to do regardless. LLPSF can then set
useDocValuesAsStored=true as a default for itself since the docValues data is
not preferable to return -- it's less precision (~1cm).
If we can agree on the above, I think it'd be a separate issue to add a feature
to actually allow LLPSF to return the lat & lon from it's DocValues. You
didn't suggest that but I thought I'd mention it.
Can you post the NPE stacktrace?
> Solr hits NPE when fl only contains DV fields and any of them is a spatial
> field
> --------------------------------------------------------------------------------
>
> Key: SOLR-11532
> URL: https://issues.apache.org/jira/browse/SOLR-11532
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
>
> Right now, Solr does not know how to decode DV value of
> LatLonPointSpatialField. Therefore, Solr will hit NPE when trying to do that,
> for example:
> - when fl contains a spatial field and it is DV + not stored
> - when fl only contains DV fields and any of them is a spatial field ( stored
> + DV ). Because SOLR-8344 will always use values from DV fields. This seems a
> common case.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
