StopwordAnalyzerBase hides Analyzer's constructor with ReuseStrategy [LUCENE-5848]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
StopwordAnalyzerBase hides Analyzer's constructor with ReuseStrategy.
It is not possible to set a ReuseStrategy when extending from StopwordAnalyzerBase.
Fix is trivial to add two extra constructors to StopwordAnalyzerBase.
Same is true for all classes extending from StopwordAnalyzerBase.
---
Migrated from [LUCENE-5848](https://issues.apache.org/jira/browse/LUCENE-5848) by Claude Quézel
Contributor guide
Research direction
Start by locating StopwordAnalyzerBase and the classes that extend it, then inspect how Analyzer exposes ReuseStrategy constructors. Add the missing constructor coverage described in the issue for StopwordAnalyzerBase and its subclasses, and run the relevant Lucene analyzer tests to confirm the classes compile and allow ReuseStrategy configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100