[
https://issues.apache.org/jira/browse/LUCENE-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064886#comment-14064886
]
Michael McCandless commented on LUCENE-5819:
--------------------------------------------
bq. Do we really need a generic solution or should this just have its own
output geared at what it does?
Well, really I just preserved that from the current block tree impl. That
byte[] has the pointer to the block, plus a couple flags
(isLeafBlock/isFloorBlock) and then any "floor block" index data (file pointer
offsets to get to the floor blocks). I agree at Outputs impl that broke these
things out would be nicer ... but I think this should probably be done
separately.
> Add block tree postings format that supports term ords
> ------------------------------------------------------
>
> Key: LUCENE-5819
> URL: https://issues.apache.org/jira/browse/LUCENE-5819
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/other
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 5.0, 4.10
>
> Attachments: LUCENE-5819.patch, LUCENE-5819.patch
>
>
> BlockTree is our default terms dictionary today, but it doesn't
> support term ords, which is an optional API in the postings format to
> retrieve the ordinal for the currently seek'd term, and also later
> seek by that ordinal e.g. to lookup the term.
> This can possibly be useful for e.g. faceting, and maybe at some point
> we can share the postings terms dict with the one used by sorted/set
> DV for cases when app wants to invert and facet on a given field.
> The older (3.x) block terms dict can easily support ords, and we have
> a Lucene41OrdsPF in test-framework, but it's not as fast / compact as
> block-tree, and doesn't (can't easily) implement an optimized
> intersect, but it could be for fields we'd want to facet on, these
> tradeoffs don't matter. It's nice to have options...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
