[
https://issues.apache.org/jira/browse/LUCENE-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-2929:
---------------------------------
Fix Version/s: (was: 4.7)
4.8
> all postings enums must explicitly declare what they need up-front.
> -------------------------------------------------------------------
>
> Key: LUCENE-2929
> URL: https://issues.apache.org/jira/browse/LUCENE-2929
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Robert Muir
> Labels: gsoc2014
> Fix For: 4.8
>
> Attachments: LUCENE-2929.patch, LUCENE-2929.patch, LUCENE-2929.patch
>
>
> Currently, the DocsEnum api assumes you *might* consumes freqs at any time.
> Additionally the DocsAndPositionsEnum api assumes you *might* consume a
> payload at any time.
> High level things such as queries know what kinds of data they need from the
> index up-front,
> and the current APIs are limiting to codecs (other than Standard, which has
> these intertwined).
> So, we either need DocsAndFreqsEnum, DocsPositionsAndPayloadsEnum, or at
> least booleans
> in the methods that create these to specify whether you want freqs or
> payloads.
> we did this for freqs in the bulkpostings API, which is good, but these
> DocsEnum apis
> are also new in 4.0 and there's no reason to introduce non-performant APIs.
> additionally when/if we add payloads to the bulkpostings API, we should make
> sure we keep
> the same trend and require you to specify you want payloads or not up-front.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
