LiveIndexWriterConfig has setters that require magical order [LUCENE-5661]
Open
legacy-jira-priority:Major
type:bug
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Specifically setRamBufferSizeMB and setMaxBufferedDocs.
Furthermore these are "live" settings on IWC, so there are potential race conditions.
It would be good if there were a better API, even if that just means documenting "if both X and Y are set, X takes precedence".
---
Migrated from [LUCENE-5661](https://issues.apache.org/jira/browse/LUCENE-5661) by Robert Muir (@rmuir)
Contributor guide
Research direction
Start by reading LiveIndexWriterConfig and the setRamBufferSizeMB and setMaxBufferedDocs setters to understand their current order-dependent behavior and live-update semantics. Done requires an agreed API or documented precedence between the settings, with the race-condition concern addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100