[
https://issues.apache.org/jira/browse/LUCENE-8264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495893#comment-16495893
]
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: https://issues.apache.org/jira/browse/LUCENE-8264
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
