[
https://issues.apache.org/jira/browse/LUCENE-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-7096:
--------------------------------
Attachment: LUCENE-7096.patch
Here is a patch simply deprecating this stuff.
We don't need to tell someone to reindex with points, only to then uninvert
with some other API. They can just add docvalues, too.
Maybe we should revert the single-valued points support as well?
> UninvertingReader needs multi-valued points support
> ---------------------------------------------------
>
> Key: LUCENE-7096
> URL: https://issues.apache.org/jira/browse/LUCENE-7096
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Attachments: LUCENE-7096.patch
>
>
> It now supports the single valued case (deprecating the legacy encoding), but
> the multi-valued stuff does not yet have a replacement.
> ideally we add a FC.getSortedNumeric(Parser..) that works from points. Unlike
> postings, points never lose frequency within a field, so its the best fit.
> when getDocCount() == size(), the field is single-valued, so this should call
> getNumeric and box that in SortedNumeric, similar to the String case.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
