[
https://issues.apache.org/jira/browse/LUCENE-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-5268:
---------------------------------------
Attachment: LUCENE-5268.patch
Patch with these changes:
* Cutover BlockTreeTermsWriter, BlockTermsWriter, FST/OrdTermsWriter
from PushFieldsConsumer to FieldsConsumer
* Changed PostingsBaseWriter to a "pull" API, with a single method
to write the current term's postings, and then added a new
PushPostingsBaseWriter that has the "push" API.
* Cutover some formats to new PostingsBaseWriter; pulsing and bloom
were nice cleanups. For the rest I just switched them to
PushPostingsBaseWriter.
* Only two PushFieldsConsumers remain: MemoryPF and RAMOnlyPF
(test-framework); I'm tempted to just cut those over and then
remove PushFieldsConsumer here.
Still a few nocommits but I think it's close ...
> Cutover more postings formats to the inverted "pull" API
> --------------------------------------------------------
>
> Key: LUCENE-5268
> URL: https://issues.apache.org/jira/browse/LUCENE-5268
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/index
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 5.0
>
> Attachments: LUCENE-5268.patch
>
>
> In LUCENE-5123, we added a new, more flexible, "pull" API for writing
> postings. This API allows the postings format to iterate the
> fields/terms/postings more than once, and mirrors the API for writing
> doc values.
> But that was just the first step (only SimpleText was cutover to the
> new API). I want to cutover more components, so we can (finally)
> e.g. play with different encodings depending on the term's postings,
> such as using a bitset for high freq DOCS_ONLY terms (LUCENE-5052).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
