You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shai Erera (JIRA)" <ji...@apache.org> on 2013/01/21 17:06:13 UTC

[jira] [Resolved] (LUCENE-4627) Migration layer for facets

     [ https://issues.apache.org/jira/browse/LUCENE-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shai Erera resolved LUCENE-4627.
--------------------------------

    Resolution: Won't Fix
    
> Migration layer for facets
> --------------------------
>
>                 Key: LUCENE-4627
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4627
>             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: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org