deprecate forceMerge/optimize and create forceMergeAndFreeze [LUCENE-8003]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Spinoff from #9025
Part of that discussion surfaced the idea that optimize/forceMerge is being discouraged, but the use-cases for forceMerge still need to be supported. Those use cases make sense when an index changes rarely.
This JIRA is to explore what that would look like.
---
Migrated from [LUCENE-8003](https://issues.apache.org/jira/browse/LUCENE-8003) by Erick Erickson (@ErickErickson)
Contributor guide
Research direction
Start by reading the discussion in #9025 and the migrated LUCENE-8003 issue. Identify the forceMerge use cases for rarely changing indexes and determine what the proposed forceMergeAndFreeze API and deprecation path would need to support. Done would require an agreed design and clearly defined scope, which the issue does not yet provide.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100