[
https://issues.apache.org/jira/browse/LUCENE-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598194#comment-13598194
]
Shai Erera commented on LUCENE-4694:
------------------------------------
bq. but docvalues is used in scoring and sorting, so this would be 100 million
binary searches. its a big damn difference.
I did not propose to ditch the per-segment efficient implementation, but rather
offer on the top-level those APIs as well. Whoever implements a
Collector/Scorer will still work with the AtomicReader instance which
implements things efficiently. Only those who need to work on top-level will
need to do SlowComposite.wrap() and work with inefficient implementations.
> Add back IndexReader.fields() -> Multi*, or discourage term vectors in some
> better way
> --------------------------------------------------------------------------------------
>
> Key: LUCENE-4694
> URL: https://issues.apache.org/jira/browse/LUCENE-4694
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Attachments: LUCENE-4694.patch
>
>
> Users can easily get term vectors from any indexreader, but not postings
> lists. this encourages them to do really slow things: like pulling term
> vectors for every single document.
> this is really really so much worse than going through multifields or
> whatever.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
