lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <>
Subject [jira] [Commented] (LUCENE-8264) Allow an option to rewrite all segments
Date Wed, 30 May 2018 23:47:00 GMT


Erick Erickson commented on LUCENE-8264:

Sorry, been away for a while

[~janhoy] re: UninvertDocValuesMergePolicyFactory. True, but wouldn't it be nice from an ops
perspective to just be able to do this as a single operation?

[~simonw] Thanks for the pointer, I'll look at this when I have a bit more breather. I think
you're right, this is probably a Solr/ES issue in terms of making it convenient from an admin
basis. I suspect it'll be something like an API command that does the wrapping magic. How
to make it maximally convenient is something we'll wrestle to the ground.

> Allow an option to rewrite all segments
> ---------------------------------------
>                 Key: LUCENE-8264
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>            Priority: Major
> For the background, see SOLR-12259.
> There are several use-cases that would be much easier, especially during upgrades, if
we could specify that all segments get rewritten. 
> One example: Upgrading 5x->6x->7x. When segments are merged, they're rewritten
into the current format. However, there's no guarantee that a particular segment _ever_ gets
merged so the 6x-7x upgrade won't necessarily be successful.
> How many merge policies support this is an open question. I propose to start with TMP
and raise other JIRAs as necessary for other merge policies.
> So far the usual response has been "re-index from scratch", but that's increasingly difficult
as systems get larger.

This message was sent by Atlassian JIRA

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

View raw message