lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4627) Migration layer for facets
Date Thu, 13 Dec 2012 12:32:16 GMT


Shai Erera commented on LUCENE-4627:

I think that Codec doesn't even need to load stuff into RAM, I mean as an optimization yes.
But this is just meant to get existing indexes workable with the new code. But I'll keep that
in mind as well.
> Migration layer for facets
> --------------------------
>                 Key: LUCENE-4627
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/facet
>            Reporter: Shai Erera
> Spin-off from LUCENE-4602 (and LUCNE-4623). It will be good if we can develop some migration
layer so that users don't need to re-index their content when we change how facets are written
in the index. Currently the two open issues are cut over to DV and index drill-down terms
w/ DOCS_ONLY, but in the future there could be other changes.
> I don't think that this layer needs to be very heavy. Something in the form of a FacetsAtomicReaderWrapper.
For instance, to support the DV migration, we can implement a PayloadFacetsAtomicReader which
translates the payload to DV API (i.e. its docValues() API will actually read from the payload).
> We'd need some API on IW I think to initialize that reader, so that data can be migrated
from payload to DV during segment merges.

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message