[
https://issues.apache.org/jira/browse/LUCENE-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212616#comment-15212616
]
Michael McCandless commented on LUCENE-7086:
--------------------------------------------
bq. Seems like it would be nicer to throw an exception when asking for a merged
Point field instead?
I think doing it lazily is dangerous: you present an inconsistent reader to
Lucene which claims to have point values (via its {{getFieldInfos}}), but then
throws an exception when you ask for them. This was causing problems in my
original patch ... it was discusses above.
I think it's better to filter the incoming readers to hide any fields that have
point values from the {{FieldInfos}}?
> SlowCompositeReaderWrapper does not support point values
> --------------------------------------------------------
>
> Key: LUCENE-7086
> URL: https://issues.apache.org/jira/browse/LUCENE-7086
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Adrien Grand
> Assignee: Michael McCandless
> Fix For: master, 6.0
>
> Attachments: LUCENE-7086.patch, LUCENE-7086.patch
>
>
> SlowCompositeReaderWrapper.getPointValues always returns null. I think this
> is trappy and we should either implement it or throw an
> UnsupportedOperationException instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
