[
https://issues.apache.org/jira/browse/LUCENE-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255284#comment-15255284
]
Andrés de la Peña commented on LUCENE-7086:
-------------------------------------------
Yes, it is a pity. In [our particular use
case|https://github.com/Stratio/cassandra-lucene-index], we can't renounce to
the huge performance improvements due to the usage of
{{EarlyTerminatingSortingCollector}}. Now that the numeric fields have
disappeared, I guess that we don't have other option than using numeric doc
values if we want to upgrade to Lucene 6.0.0. Should we open a new ticket for
fixing this incompatibility within {{SortingMergePolicy}} and point fields, or
is it covered by any other ticket? We can't wait to use the amazing point
fields!
It would also be good to take a look to [the problems paging over search
results|http://permalink.gmane.org/gmane.comp.jakarta.lucene.user/60076] with
{{EarlyTerminatingSortingCollector}}.
> 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]
