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

Shai Erera resolved LUCENE-4564.
--------------------------------
    Resolution: Won't Fix

The facet module has been rewritten twice during 4.x, requiring an effective 
rewrite on the application already. Therefore I think it's fair to assume that 
this issue is no longer relevant. I'm closing it and we can reopen if needed.

> Add taxonomy index upgrade utility
> ----------------------------------
>
>                 Key: LUCENE-4564
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4564
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: modules/facet
>            Reporter: Shai Erera
>            Assignee: Shai Erera
>            Priority: Blocker
>             Fix For: Trunk
>
>
> Currently there's no way for an app to upgrade a taxonomy index to the newest 
> index format. The problem is, that unlike search indexes which may merge 
> segments often, the taxonomy index is not likely to do many merges. At some 
> point, most taxonomies become fixed (i.e. new categories are not/rarely 
> added), and therefore it could be that some old segments will never get 
> merged.
> When we'll release Lucene 5.0, support for 3x indexes will be removed, and so 
> taxonomies that were created w/ 3x won't be read anymore.
> While one can use IndexUpgrader (I think) to upgrade the taxonomy index, it 
> may not be so trivial for users to realize that, as it may not be so evident 
> from DirTaxoWriter/Reader API that there's a regular Lucene index behind the 
> scenes.
> A tool, like TaxonomyUpgraderTool, even if simple and using IndexUpgrader, 
> may make it more convenient for user to upgrade their taxonomy index.
> Opening as a placeholder for 5.0. Also marking as blocker, so we don't forget 
> about it before the release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to