Stop Words Should Not Be Hard Coded
Open
- Dominant language
- Java
- Stars
- 6.1k
- Forks
- 1.5k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 189
Description
During text index creation, we pass in a hard coded list of stop words which limits the vocabulary that we can use to filter words before indexing.
We should use Lucene's StopFilter and read the list of stop words from a file, thus allowing users flexibility in terms of filtering words.
Contributor guide
Research direction
Start by locating the text index creation path and the hard-coded stop-word list described in the issue. Read how Lucene's StopFilter is used there and identify the existing configuration or resource-loading conventions; done means users can provide a stop-word file that is read during indexing instead of relying on the fixed list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100